Device product pages

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
+
+<DeviceFeatures features="mA,rfid,sponsorship" />
+
+https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_Charger_OCPP1.6_ImplementationOverview%20_v1.8_FW1.6.6.pdf
+
+
+<DeviceConfig code={`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://<evcc-address>:8887/<stationid>. 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://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
+      connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
+      remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
+      idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
+      connecttimeout: 5m # Timeout for the registration of the charging point, optional
+      meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
+      metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />
+
+<SponsorshipRequired />
+

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)
+
+<DeviceFeatures features="mA,sponsorship" />
+
+<DeviceConfig code={`chargers:
+    - name: my_charger
+      type: template
+      template: abl-em4
+
+      # Modbus TCP
+      modbus: tcpip
+      id: 255
+      host: 192.0.2.2 # Hostname
+      port: 502 # Port`} advanced={`chargers:
+    - name: my_charger
+      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`} />
+
+<SponsorshipRequired />
+

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
+
+<DeviceFeatures features="mA,sponsorship" />
+
+<DeviceConfig code={`chargers:
+    - name: my_charger
+      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`}  />
+
+<SponsorshipRequired />
+

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
+
+<DeviceFeatures features="mA,sponsorship" />
+
+<DeviceConfig code={`chargers:
+    - name: my_charger
+      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`}  />
+
+<SponsorshipRequired />
+

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
+
+<DeviceFeatures features="mA,rfid,sponsorship" />
+
+<DeviceConfig code={`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://<evcc-address>:8887/<stationid>. 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://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
+      connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
+      remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
+      idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
+      connecttimeout: 5m # Timeout for the registration of the charging point, optional
+      meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
+      metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />
+
+<SponsorshipRequired />
+

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
+
+<DeviceFeatures features="mA,rfid,sponsorship" />
+
+<DeviceConfig code={`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://<evcc-address>:8887/<stationid>. 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://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
+      connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
+      remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
+      idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
+      connecttimeout: 5m # Timeout for the registration of the charging point, optional
+      meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
+      metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />
+
+<SponsorshipRequired />
+

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
+
+<DeviceFeatures features="mA,rfid,sponsorship" />
+
+<DeviceConfig code={`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://<evcc-address>:8887/<stationid>. 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://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
+      connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
+      remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
+      idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
+      connecttimeout: 5m # Timeout for the registration of the charging point, optional
+      meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
+      metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />
+
+<SponsorshipRequired />
+

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
+
+<DeviceFeatures features="mA,rfid,1p3p,sponsorship" />
+
+<DeviceConfig code={`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://<evcc-address>:8887/<stationid>. 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://<evcc-address>:8887/<stationid>. Most charging stations automatically add the ID internally. (optional)
+      connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (optional)
+      remotestart: # Always start a remote transaction (RemoteStartTransaction) as soon as a vehicle is connected, Only enable this option if there is no way to initiate transactions from the charger side! This is only the case if e.g. no RFID reader is available and charging processes would have to be released individually via app. Normally, the charger should always be configured at the device so that either an RFID card is used for activation or the charger is set to "Autostart", "Free Charging" or similar. First check the documentation and configuration possibilities of the charger, ask the manufacturer if necessary! (optional)
+      idtag: evcc # Identifier used for authentication of external transactions (RemoteStartTransaction), This option is only required in exceptional cases if the charger requires a specific token for accepting external transactions. (optional)
+      connecttimeout: 5m # Timeout for the registration of the charging point, optional
+      meterinterval: 10s # Transmission interval of meter values (MeterValueSampleInterval), optional
+      metervalues: Energy.Active.Import.Register,Power.Active.Import,SoC,Current.Offered,Power.Offered,Current.Import,Voltage # Manual specification of the meter values to be configured (MeterValuesSampledData), optional`} />
+
+<SponsorshipRequired />
+

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
+
+<DeviceFeatures features="sponsorship" />
+
+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.
+
+
+<DeviceConfig code={`chargers:
+    - name: my_charger
+      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`}  />
+
+<SponsorshipRequired />
+