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 000000000..60be96ea3 --- /dev/null +++ b/docs/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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 + + +: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: # 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://: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 | +| 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 new file mode 100644 index 000000000..8e7256023 --- /dev/null +++ b/docs/devices-next/chargers/abb-terra-ac.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `abb` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..52b0e9764 --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..bcf4875af --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..a43625883 --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..d2d0b0e47 --- /dev/null +++ b/docs/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..83fc283b9 --- /dev/null +++ b/docs/devices-next/chargers/abl-emh1.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..bb41536ce --- /dev/null +++ b/docs/devices-next/chargers/abl-emh2-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a6f929ada --- /dev/null +++ b/docs/devices-next/chargers/abl-emh2.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..b66a41647 --- /dev/null +++ b/docs/devices-next/chargers/abl-emh3-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a1c81b858 --- /dev/null +++ b/docs/devices-next/chargers/alfen-eve-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..9de797d0e --- /dev/null +++ b/docs/devices-next/chargers/alfen-eve.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `alfen` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..72674e9ba --- /dev/null +++ b/docs/devices-next/chargers/alpha-innotec.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9a12b61cd --- /dev/null +++ b/docs/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..722f405eb --- /dev/null +++ b/docs/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..ded259ea8 --- /dev/null +++ b/docs/devices-next/chargers/alphatec-wallbox-power.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..df9e946a2 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..f35030084 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..eb0bf2a49 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..66059a382 --- /dev/null +++ b/docs/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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). + + + +
+
+ +
+
+ +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/ampure-next.mdx b/docs/devices-next/chargers/ampure-next.mdx new file mode 100644 index 000000000..ba167b1d6 --- /dev/null +++ b/docs/devices-next/chargers/ampure-next.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..d76470da1 --- /dev/null +++ b/docs/devices-next/chargers/ampure-unite.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..2f8efc24b --- /dev/null +++ b/docs/devices-next/chargers/audi-wallbox-plus.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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. + + + +
+
+ +
+
+ +## 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 000000000..26d8b7824 --- /dev/null +++ b/docs/devices-next/chargers/audi-wallbox-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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 new file mode 100644 index 000000000..742306ff6 --- /dev/null +++ b/docs/devices-next/chargers/autel-ac-compact.mdx @@ -0,0 +1,69 @@ +--- +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'; +import DeviceFeatures from '@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” +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..925ef26b6 --- /dev/null +++ b/docs/devices-next/chargers/autel-ac-maxicharger.mdx @@ -0,0 +1,69 @@ +--- +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'; +import DeviceFeatures from '@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” +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..666bef2c7 --- /dev/null +++ b/docs/devices-next/chargers/autoaid-business-wallbox.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..1973533d1 --- /dev/null +++ b/docs/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..d09bf01d4 --- /dev/null +++ b/docs/devices-next/chargers/avm-fritzdect.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..d4790df51 --- /dev/null +++ b/docs/devices-next/chargers/bender-cc612.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/bender-cc613.mdx b/docs/devices-next/chargers/bender-cc613.mdx new file mode 100644 index 000000000..e97d16a6e --- /dev/null +++ b/docs/devices-next/chargers/bender-cc613.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/bender-icc1314.mdx b/docs/devices-next/chargers/bender-icc1314.mdx new file mode 100644 index 000000000..238fd077b --- /dev/null +++ b/docs/devices-next/chargers/bender-icc1314.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/bender-icc1324.mdx b/docs/devices-next/chargers/bender-icc1324.mdx new file mode 100644 index 000000000..df7f6adec --- /dev/null +++ b/docs/devices-next/chargers/bender-icc1324.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..dc43e78d6 --- /dev/null +++ b/docs/devices-next/chargers/bmw-i-wallbox.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..3b82360be --- /dev/null +++ b/docs/devices-next/chargers/bosch-sg-ready.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + +
+
+ +
+
+ +## Template Parameter `emsesp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| 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 new file mode 100644 index 000000000..d1cf43665 --- /dev/null +++ b/docs/devices-next/chargers/bosch-x-change.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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
`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 000000000..75fb04d2b --- /dev/null +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..49bb5b315 --- /dev/null +++ b/docs/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..03269f36a --- /dev/null +++ b/docs/devices-next/chargers/buderus-sg-ready.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + +
+
+ +
+
+ +## Template Parameter `emsesp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| 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 new file mode 100644 index 000000000..3b28e8d05 --- /dev/null +++ b/docs/devices-next/chargers/cfos-power-brain-solar.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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: +1) Home -> disable Load Balancing (Monitoring Mode) +2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..0673ffce6 --- /dev/null +++ b/docs/devices-next/chargers/cfos-power-brain.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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: +1) Home -> disable Load Balancing (Monitoring Mode) +2) Configuration -> Hardware - Phase switch / Relais 2 (enable phase switching) + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..f19b66651 --- /dev/null +++ b/docs/devices-next/chargers/charge-amps-halo.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..f361056bb --- /dev/null +++ b/docs/devices-next/chargers/compleo-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..58b229a28 --- /dev/null +++ b/docs/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..5b5b7f6f4 --- /dev/null +++ b/docs/devices-next/chargers/cubos-c11e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..88e84f5b3 --- /dev/null +++ b/docs/devices-next/chargers/cubos-c22e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..4fa2bab61 --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-connect-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..023182bde --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..c91a84611 --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-pro-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..df315d294 --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..96e72d97f --- /dev/null +++ b/docs/devices-next/chargers/cupra-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/dadapower-premium-wallbox.mdx b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx new file mode 100644 index 000000000..034e39fb8 --- /dev/null +++ b/docs/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/daheimladen-wallbox.mdx b/docs/devices-next/chargers/daheimladen-wallbox.mdx new file mode 100644 index 000000000..5fd562df4 --- /dev/null +++ b/docs/devices-next/chargers/daheimladen-wallbox.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..fdda9e4b4 --- /dev/null +++ b/docs/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..735e5ff24 --- /dev/null +++ b/docs/devices-next/chargers/delta-ac-max-basic.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..80351850d --- /dev/null +++ b/docs/devices-next/chargers/delta-ac-max-smart.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..15e80918f --- /dev/null +++ b/docs/devices-next/chargers/delta-slim-charger.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..ad5af2376 --- /dev/null +++ b/docs/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..fdd553e7c --- /dev/null +++ b/docs/devices-next/chargers/demo-charger.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..f21e85ea7 --- /dev/null +++ b/docs/devices-next/chargers/e-on-drive-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..a9d38b447 --- /dev/null +++ b/docs/devices-next/chargers/e-on-drive-vbox.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..875c7ba21 --- /dev/null +++ b/docs/devices-next/chargers/e3-dc-easy-connect.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..640283b97 --- /dev/null +++ b/docs/devices-next/chargers/easee-charge-core.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..9281f67ed --- /dev/null +++ b/docs/devices-next/chargers/easee-charge-lite.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..b10056394 --- /dev/null +++ b/docs/devices-next/chargers/easee-charge.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..4a1fe3c30 --- /dev/null +++ b/docs/devices-next/chargers/easee-home.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..66b83e51a --- /dev/null +++ b/docs/devices-next/chargers/ebee-wallbox.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/echarge-cph1.mdx b/docs/devices-next/chargers/echarge-cph1.mdx new file mode 100644 index 000000000..bfa1f689d --- /dev/null +++ b/docs/devices-next/chargers/echarge-cph1.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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` + + +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.mdx b/docs/devices-next/chargers/echarge-cph2.mdx new file mode 100644 index 000000000..afb92ecab --- /dev/null +++ b/docs/devices-next/chargers/echarge-cph2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..4ee3d8e0a --- /dev/null +++ b/docs/devices-next/chargers/echarge-cpm2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..2074d3283 --- /dev/null +++ b/docs/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..4657d6d47 --- /dev/null +++ b/docs/devices-next/chargers/edgetech-smart-evse.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/eebus-compatible.mdx b/docs/devices-next/chargers/eebus-compatible.mdx new file mode 100644 index 000000000..5364b6768 --- /dev/null +++ b/docs/devices-next/chargers/eebus-compatible.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..d15f05119 --- /dev/null +++ b/docs/devices-next/chargers/elco.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..0e30190af --- /dev/null +++ b/docs/devices-next/chargers/elecq-biz.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..ce45e09f9 --- /dev/null +++ b/docs/devices-next/chargers/elecq-home.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..16b99fe07 --- /dev/null +++ b/docs/devices-next/chargers/elecq-station.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..90d8681e2 --- /dev/null +++ b/docs/devices-next/chargers/eledio-go.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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 + + +: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: # 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://: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 | +| 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 new file mode 100644 index 000000000..9ac9b7eaf --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-connect-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..55b20fb33 --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..8774f9cb1 --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-pro-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..81bfab39d --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..1510d23b4 --- /dev/null +++ b/docs/devices-next/chargers/elli-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/em2go-home.mdx b/docs/devices-next/chargers/em2go-home.mdx new file mode 100644 index 000000000..9b1386eb2 --- /dev/null +++ b/docs/devices-next/chargers/em2go-home.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..16dd03fb3 --- /dev/null +++ b/docs/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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) + + + +
+
+ +
+
+ +## Template Parameter `em2go` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/chargers/enercab-smart.mdx b/docs/devices-next/chargers/enercab-smart.mdx new file mode 100644 index 000000000..fba830a35 --- /dev/null +++ b/docs/devices-next/chargers/enercab-smart.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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 + + +: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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a54f60ce1 --- /dev/null +++ b/docs/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..bdd7dcfdc --- /dev/null +++ b/docs/devices-next/chargers/ensto-chago-wallbox.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..46fb1a546 --- /dev/null +++ b/docs/devices-next/chargers/entratek-power-dot-fix.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..71d8a749f --- /dev/null +++ b/docs/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..95b0af198 --- /dev/null +++ b/docs/devices-next/chargers/esl-walli-light.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/esystems-ghostone.mdx b/docs/devices-next/chargers/esystems-ghostone.mdx new file mode 100644 index 000000000..656f480c4 --- /dev/null +++ b/docs/devices-next/chargers/esystems-ghostone.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..1abb809de --- /dev/null +++ b/docs/devices-next/chargers/etrel-inch-duo.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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. + + +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 new file mode 100644 index 000000000..3fcfaa1a8 --- /dev/null +++ b/docs/devices-next/chargers/etrel-inch.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..a1725cf34 --- /dev/null +++ b/docs/devices-next/chargers/evbox-elvi.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 # 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 # Meter ID, optional + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (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://: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 | +| 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 new file mode 100644 index 000000000..c051a79be --- /dev/null +++ b/docs/devices-next/chargers/evbox-livo.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..90e02cec3 --- /dev/null +++ b/docs/devices-next/chargers/evse-din.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/evse-wifi.mdx b/docs/devices-next/chargers/evse-wifi.mdx new file mode 100644 index 000000000..3ab825742 --- /dev/null +++ b/docs/devices-next/chargers/evse-wifi.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..929cee03b --- /dev/null +++ b/docs/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/free2move-eprowallbox.mdx b/docs/devices-next/chargers/free2move-eprowallbox.mdx new file mode 100644 index 000000000..0ca80e897 --- /dev/null +++ b/docs/devices-next/chargers/free2move-eprowallbox.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..472f0e6e9 --- /dev/null +++ b/docs/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..54162875a --- /dev/null +++ b/docs/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..b816afe90 --- /dev/null +++ b/docs/devices-next/chargers/garo-glb.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..f4a0be692 --- /dev/null +++ b/docs/devices-next/chargers/garo-glbplus.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9681b1769 --- /dev/null +++ b/docs/devices-next/chargers/garo-ls4-compact.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..fd903e6a8 --- /dev/null +++ b/docs/devices-next/chargers/garo-ls4.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..3b22d87c4 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..43576e6da --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-gemini.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. +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-homefix.mdx b/docs/devices-next/chargers/go-e-charger-homefix.mdx new file mode 100644 index 000000000..dd49fa1c9 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-homefix.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..fde6551ae --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-homeplus.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. +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 000000000..a4b68888c --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..bcca58b06 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-pro.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..8b5e3fa11 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..4b1955168 --- /dev/null +++ b/docs/devices-next/chargers/go-e-charger-v3.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. +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/hardy-barth-cph1.mdx b/docs/devices-next/chargers/hardy-barth-cph1.mdx new file mode 100644 index 000000000..a6e7486f0 --- /dev/null +++ b/docs/devices-next/chargers/hardy-barth-cph1.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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` + + +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 000000000..c855f9c6a --- /dev/null +++ b/docs/devices-next/chargers/hardy-barth-cph2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..5461accef --- /dev/null +++ b/docs/devices-next/chargers/hardy-barth-cpm2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + + + 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 000000000..8a55164bb --- /dev/null +++ b/docs/devices-next/chargers/heidelberg-energy-control.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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). + + + +
+
+ +
+
+ +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..4ade854e7 --- /dev/null +++ b/docs/devices-next/chargers/hesotec-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/hesotec-esat.mdx b/docs/devices-next/chargers/hesotec-esat.mdx new file mode 100644 index 000000000..fc8c94f01 --- /dev/null +++ b/docs/devices-next/chargers/hesotec-esat.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..71b516285 --- /dev/null +++ b/docs/devices-next/chargers/home-assistant-switch.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..a41574906 --- /dev/null +++ b/docs/devices-next/chargers/homecharge-homecharger.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..7bd57444d --- /dev/null +++ b/docs/devices-next/chargers/homematic-ip.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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
`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
`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 new file mode 100644 index 000000000..f376fade9 --- /dev/null +++ b/docs/devices-next/chargers/homewizard.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..19973f809 --- /dev/null +++ b/docs/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..850fe1827 --- /dev/null +++ b/docs/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..d5d4f73d0 --- /dev/null +++ b/docs/devices-next/chargers/idm.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`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 new file mode 100644 index 000000000..873924cd4 --- /dev/null +++ b/docs/devices-next/chargers/index.mdx @@ -0,0 +1,3137 @@ +--- +title: Chargers +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; + +# Chargers + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/chargers/innogy-ebox.mdx b/docs/devices-next/chargers/innogy-ebox.mdx new file mode 100644 index 000000000..b0c089795 --- /dev/null +++ b/docs/devices-next/chargers/innogy-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/inro-pantabox.mdx b/docs/devices-next/chargers/inro-pantabox.mdx new file mode 100644 index 000000000..a2f84f980 --- /dev/null +++ b/docs/devices-next/chargers/inro-pantabox.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..c5c666e2a --- /dev/null +++ b/docs/devices-next/chargers/juice-charger-me.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..ffddbe002 --- /dev/null +++ b/docs/devices-next/chargers/junkers-sg-ready.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + +
+
+ +
+
+ +## Template Parameter `emsesp` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| 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 new file mode 100644 index 000000000..23065d5cc --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..d490e298e --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..2cdd5890c --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..a46778ed7 --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e16f10982 --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..73f1669eb --- /dev/null +++ b/docs/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `Kathrein` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..5824fc655 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p20.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..fe912bfb0 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e00b2f574 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..c3cae3804 --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9134f4aaa --- /dev/null +++ b/docs/devices-next/chargers/keba-kecontact-p40.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..41f0a661e --- /dev/null +++ b/docs/devices-next/chargers/kermi-x-center-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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
`watchdog` | | Standard: `60s` | no | + 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 000000000..331a4aa12 --- /dev/null +++ b/docs/devices-next/chargers/kontron-solar-charger.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..4f8e58f23 --- /dev/null +++ b/docs/devices-next/chargers/kostal-enector.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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. +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 Type
`modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/kse-wbx16.mdx b/docs/devices-next/chargers/kse-wbx16.mdx new file mode 100644 index 000000000..ce84b915b --- /dev/null +++ b/docs/devices-next/chargers/kse-wbx16.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/ladefoxx-evload.mdx b/docs/devices-next/chargers/ladefoxx-evload.mdx new file mode 100644 index 000000000..e512073eb --- /dev/null +++ b/docs/devices-next/chargers/ladefoxx-evload.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..51ad7ecc7 --- /dev/null +++ b/docs/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..a881d6a22 --- /dev/null +++ b/docs/devices-next/chargers/lambda-eu-l-series.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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: + +- E-Meter communication type: "ModBus Client" +- E-Meter measuring point: "Pos. E-Überschuss" + + + +
+
+ +
+
+ +## 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
`watchdog` | | Standard: `60s` | no | + 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 000000000..292649613 --- /dev/null +++ b/docs/devices-next/chargers/lrt-home-essentialplus.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `alphatec` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..492b2a5f7 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amedio-professional.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..72392fae6 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..fcd791fff --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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. +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 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 new file mode 100644 index 000000000..ce8d1adde --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-icc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..3f412d2d3 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..7821357b2 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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. +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 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 new file mode 100644 index 000000000..022f906ab --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-premium.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..e0427d76c --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-professional.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..2353c03c3 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..13e712a87 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..690adaa88 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-smart-acu.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..8a67f8225 --- /dev/null +++ b/docs/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..ef35db5e3 --- /dev/null +++ b/docs/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..db72ea1b5 --- /dev/null +++ b/docs/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..56b6869e8 --- /dev/null +++ b/docs/devices-next/chargers/my-pv-ac-thor.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..6c4d26548 --- /dev/null +++ b/docs/devices-next/chargers/mystrom-switch.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..5234311b3 --- /dev/null +++ b/docs/devices-next/chargers/nibe-ap-aw10.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..b371a7216 --- /dev/null +++ b/docs/devices-next/chargers/novelan-wpr-net.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1e986ab1f --- /dev/null +++ b/docs/devices-next/chargers/nrgkick-connect.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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) + + + +
+
+ +
+
+ +## Template Parameter `nrgkick-connect` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | 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 new file mode 100644 index 000000000..731254e32 --- /dev/null +++ b/docs/devices-next/chargers/nrgkick-gen2.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `nrggen2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e32c8685f --- /dev/null +++ b/docs/devices-next/chargers/obo-bettermann-ion.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..e9af002d6 --- /dev/null +++ b/docs/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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. +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..1781e8329 --- /dev/null +++ b/docs/devices-next/chargers/openevse.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..10128a8b7 --- /dev/null +++ b/docs/devices-next/chargers/openwb-pro.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..0055c2a51 --- /dev/null +++ b/docs/devices-next/chargers/openwb-series2.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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. + + +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 000000000..414e7305f --- /dev/null +++ b/docs/devices-next/chargers/openwb-software-2-x.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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: + +* 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 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 new file mode 100644 index 000000000..8e62156d6 --- /dev/null +++ b/docs/devices-next/chargers/optec-mobility-one.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/orbis-viaris.mdx b/docs/devices-next/chargers/orbis-viaris.mdx new file mode 100644 index 000000000..a14c17ebd --- /dev/null +++ b/docs/devices-next/chargers/orbis-viaris.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..c7846c1b5 --- /dev/null +++ b/docs/devices-next/chargers/pc-electric-garo.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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! + + + +
+
+ +
+
+ +## 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 000000000..bd59abdf0 --- /dev/null +++ b/docs/devices-next/chargers/peblar-business.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `peblar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1a394245f --- /dev/null +++ b/docs/devices-next/chargers/peblar-home-plus.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `peblar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..a5477b7c1 --- /dev/null +++ b/docs/devices-next/chargers/peblar-home.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `peblar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..240914c6a --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-charx.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..bb788fb62 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..1f188c198 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth-3g.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..fea82ca04 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-cbc-rcm-eth.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..938d809aa --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-3g-xp.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..d0f678814 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-cc-ac1-m3-rcm-eth-xp.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1829844f5 --- /dev/null +++ b/docs/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/plugchoice.mdx b/docs/devices-next/chargers/plugchoice.mdx new file mode 100644 index 000000000..47d43d6a4 --- /dev/null +++ b/docs/devices-next/chargers/plugchoice.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + +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. + + + +
+
+ +
+
+ +## Template Parameter `plugchoice` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..8da6c0122 --- /dev/null +++ b/docs/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..96740a3b3 --- /dev/null +++ b/docs/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..4758fbfb7 --- /dev/null +++ b/docs/devices-next/chargers/porsche-wallbox.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..8703e415d --- /dev/null +++ b/docs/devices-next/chargers/pracht-alpha-xt.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`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 new file mode 100644 index 000000000..2cc9c234c --- /dev/null +++ b/docs/devices-next/chargers/pracht-mono-xt.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`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 new file mode 100644 index 000000000..f141479da --- /dev/null +++ b/docs/devices-next/chargers/pracht-pni.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`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-xtplus.mdx b/docs/devices-next/chargers/pracht-xtplus.mdx new file mode 100644 index 000000000..622408444 --- /dev/null +++ b/docs/devices-next/chargers/pracht-xtplus.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`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 new file mode 100644 index 000000000..a66ceed5e --- /dev/null +++ b/docs/devices-next/chargers/pulsares-simplebox.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/pulsatrix.mdx b/docs/devices-next/chargers/pulsatrix.mdx new file mode 100644 index 000000000..f4cff6d58 --- /dev/null +++ b/docs/devices-next/chargers/pulsatrix.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..3e038e75e --- /dev/null +++ b/docs/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/roth-thermoaura.mdx b/docs/devices-next/chargers/roth-thermoaura.mdx new file mode 100644 index 000000000..eddd224c4 --- /dev/null +++ b/docs/devices-next/chargers/roth-thermoaura.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e070ca710 --- /dev/null +++ b/docs/devices-next/chargers/roth-thermoterra.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..75934dd0a --- /dev/null +++ b/docs/devices-next/chargers/schneider-evlink-pro.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..c05e28898 --- /dev/null +++ b/docs/devices-next/chargers/schrack-i-charge-cion.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..da05661ce --- /dev/null +++ b/docs/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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). + + + +
+
+ +
+
+ +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..0f184ee5b --- /dev/null +++ b/docs/devices-next/chargers/senec-wallbox-pro.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..53f90b1b1 --- /dev/null +++ b/docs/devices-next/chargers/shelly-1.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 000000000..3268edd48 --- /dev/null +++ b/docs/devices-next/chargers/shelly-plug-s.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 000000000..f30c032b2 --- /dev/null +++ b/docs/devices-next/chargers/shelly-plus-1.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 000000000..401e8a204 --- /dev/null +++ b/docs/devices-next/chargers/shelly-pro-1.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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/siemens-versicharge-gen3.mdx b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx new file mode 100644 index 000000000..55292881e --- /dev/null +++ b/docs/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `versicharge` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..5d196237b --- /dev/null +++ b/docs/devices-next/chargers/skoda-charger-connect.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..8c46d9f0f --- /dev/null +++ b/docs/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..f643ea4cb --- /dev/null +++ b/docs/devices-next/chargers/skoda-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..0cac23d8b --- /dev/null +++ b/docs/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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. + + + +
+
+ +
+
+ +## 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 000000000..548e49562 --- /dev/null +++ b/docs/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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 000000000..6d767cf83 --- /dev/null +++ b/docs/devices-next/chargers/sma-echarger.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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.mdx b/docs/devices-next/chargers/sma-ev-charger.mdx new file mode 100644 index 000000000..ab28c270e --- /dev/null +++ b/docs/devices-next/chargers/sma-ev-charger.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..91dcc717b --- /dev/null +++ b/docs/devices-next/chargers/smartfox-pro-charger.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/chargers/smartwb.mdx b/docs/devices-next/chargers/smartwb.mdx new file mode 100644 index 000000000..ac159049c --- /dev/null +++ b/docs/devices-next/chargers/smartwb.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..454f2f789 --- /dev/null +++ b/docs/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `keba-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..a482e58ab --- /dev/null +++ b/docs/devices-next/chargers/solax-x3-evc.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/sonnen-sonnencharger.mdx b/docs/devices-next/chargers/sonnen-sonnencharger.mdx new file mode 100644 index 000000000..8534d5ad5 --- /dev/null +++ b/docs/devices-next/chargers/sonnen-sonnencharger.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..92b0a3e73 --- /dev/null +++ b/docs/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..7dde8b794 --- /dev/null +++ b/docs/devices-next/chargers/stark-in-strom-easy.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..7315fa8f2 --- /dev/null +++ b/docs/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..76a75de3d --- /dev/null +++ b/docs/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..2616e2105 --- /dev/null +++ b/docs/devices-next/chargers/sungrow-ac011e-01.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/sungrow-ac011e.mdx b/docs/devices-next/chargers/sungrow-ac011e.mdx new file mode 100644 index 000000000..10d6fe464 --- /dev/null +++ b/docs/devices-next/chargers/sungrow-ac011e.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a2de97b65 --- /dev/null +++ b/docs/devices-next/chargers/sungrow-ac22e-01.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..ebfdf52e2 --- /dev/null +++ b/docs/devices-next/chargers/tasmota-single-phase.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..c2eb2754e --- /dev/null +++ b/docs/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..cca6abc85 --- /dev/null +++ b/docs/devices-next/chargers/technisat-technivolt.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..90c54de74 --- /dev/null +++ b/docs/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..fb3948f5b --- /dev/null +++ b/docs/devices-next/chargers/tessie.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..670a1a018 --- /dev/null +++ b/docs/devices-next/chargers/tigo-go-ev-charger.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9ea1d1532 --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..e1b17ecd3 --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..a9fb515a0 --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..46ff740d0 --- /dev/null +++ b/docs/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..ece700ec9 --- /dev/null +++ b/docs/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..e8b259f62 --- /dev/null +++ b/docs/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..17964e103 --- /dev/null +++ b/docs/devices-next/chargers/ubitricity-heinz.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/v2c-trydan.mdx b/docs/devices-next/chargers/v2c-trydan.mdx new file mode 100644 index 000000000..767ea9d46 --- /dev/null +++ b/docs/devices-next/chargers/v2c-trydan.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..965d5edea --- /dev/null +++ b/docs/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..8e93ef5f7 --- /dev/null +++ b/docs/devices-next/chargers/vestel-connect-plus.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..614bc3563 --- /dev/null +++ b/docs/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1164cd519 --- /dev/null +++ b/docs/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `victron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..075d4daf0 --- /dev/null +++ b/docs/devices-next/chargers/victron-ev-charging-station.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `victron-evcs` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..db1f8afe3 --- /dev/null +++ b/docs/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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). + + + 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`} /> +
+
+ +
+
+ +## 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...
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 new file mode 100644 index 000000000..32d53a928 --- /dev/null +++ b/docs/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..b13cbc5ff --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..8f7d29b54 --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..b351b2d27 --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +The usage of phase switching is currently not possible in evcc. + +The identification of a vehicle using the RFID card is not possible. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..5777e27a6 --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..637e6696c --- /dev/null +++ b/docs/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/volt-time-one.mdx b/docs/devices-next/chargers/volt-time-one.mdx new file mode 100644 index 000000000..6988fe1d8 --- /dev/null +++ b/docs/devices-next/chargers/volt-time-one.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1ddde96b1 --- /dev/null +++ b/docs/devices-next/chargers/volt-time-source-2.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1a2fee8ad --- /dev/null +++ b/docs/devices-next/chargers/volt-time-source-2s.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e73d41401 --- /dev/null +++ b/docs/devices-next/chargers/volt-time-source.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `volttime` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..72a31261e --- /dev/null +++ b/docs/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/wallbe-eco.mdx b/docs/devices-next/chargers/wallbe-eco.mdx new file mode 100644 index 000000000..e96635cb4 --- /dev/null +++ b/docs/devices-next/chargers/wallbe-eco.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/wallbe-pro.mdx b/docs/devices-next/chargers/wallbe-pro.mdx new file mode 100644 index 000000000..4d415aa32 --- /dev/null +++ b/docs/devices-next/chargers/wallbe-pro.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `phoenix-ev-eth` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..d66b58d6c --- /dev/null +++ b/docs/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..64363b10e --- /dev/null +++ b/docs/devices-next/chargers/wallbox-commander-2.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..c003d7a72 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..c687f70f4 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-copper-sb.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..4663ff965 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..54b1a0869 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-max.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..d42137578 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..d87bbf174 --- /dev/null +++ b/docs/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..ff2f4deea --- /dev/null +++ b/docs/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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). + + + +
+
+ +
+
+ +## Template Parameter `heidelberg` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + + + diff --git a/docs/devices-next/chargers/webasto-live.mdx b/docs/devices-next/chargers/webasto-live.mdx new file mode 100644 index 000000000..d2662515a --- /dev/null +++ b/docs/devices-next/chargers/webasto-live.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `bender-cc` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/chargers/webasto-next.mdx b/docs/devices-next/chargers/webasto-next.mdx new file mode 100644 index 000000000..79c26b527 --- /dev/null +++ b/docs/devices-next/chargers/webasto-next.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..4034c485d --- /dev/null +++ b/docs/devices-next/chargers/webasto-unite.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `vestel` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..49eef9a31 --- /dev/null +++ b/docs/devices-next/chargers/weidmuller-ac-smart.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..11e9e70fa --- /dev/null +++ b/docs/devices-next/chargers/wolf-bwl.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..c25106189 --- /dev/null +++ b/docs/devices-next/chargers/wolf-bws.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `luxtronik` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..dd6daf2be --- /dev/null +++ b/docs/devices-next/chargers/zaptec-go-2.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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
`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 000000000..eeedfc502 --- /dev/null +++ b/docs/devices-next/chargers/zaptec-go-ocpp.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 + +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..1fdcad481 --- /dev/null +++ b/docs/devices-next/chargers/zaptec-go.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..2c1606053 --- /dev/null +++ b/docs/devices-next/chargers/zaptec-pro.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..83d9f14e0 --- /dev/null +++ b/docs/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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: + +- E-Meter communication type: "ModBus Client" +- E-Meter measuring point: "Pos. E-Überschuss" + + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..992e47c29 --- /dev/null +++ b/docs/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..8ac4e621e --- /dev/null +++ b/docs/devices-next/meters/a-tronix.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Delay
`delay` | | Standard: `100ms` | no | + diff --git a/docs/devices-next/meters/abb-a43.mdx b/docs/devices-next/meters/abb-a43.mdx new file mode 100644 index 000000000..64fea3c43 --- /dev/null +++ b/docs/devices-next/meters/abb-a43.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..cb074be96 --- /dev/null +++ b/docs/devices-next/meters/abb-a44.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..6989f0f20 --- /dev/null +++ b/docs/devices-next/meters/abb-b23.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`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 000000000..7303cb6b4 --- /dev/null +++ b/docs/devices-next/meters/abb-b24.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `abb-ab` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/acrel-adw300.mdx b/docs/devices-next/meters/acrel-adw300.mdx new file mode 100644 index 000000000..cbf325c0a --- /dev/null +++ b/docs/devices-next/meters/acrel-adw300.mdx @@ -0,0 +1,124 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `acrel-adw300` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..56cc7b5a3 --- /dev/null +++ b/docs/devices-next/meters/ads-tec-storaxe.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..b0d2bee81 --- /dev/null +++ b/docs/devices-next/meters/alpha-ess-storion-smile.mdx @@ -0,0 +1,181 @@ +--- +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'; +import DeviceFeatures from '@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`. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `alpha-ess-smile` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 000000000..9a180a26a --- /dev/null +++ b/docs/devices-next/meters/ampere-ampere-storagepro.mdx @@ -0,0 +1,155 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `saj-h2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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/anker-micro-inverter.mdx b/docs/devices-next/meters/anker-micro-inverter.mdx new file mode 100644 index 000000000..76cf9be30 --- /dev/null +++ b/docs/devices-next/meters/anker-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/apsystems-ez1.mdx b/docs/devices-next/meters/apsystems-ez1.mdx new file mode 100644 index 000000000..7eb95ad3c --- /dev/null +++ b/docs/devices-next/meters/apsystems-ez1.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..21bc25f14 --- /dev/null +++ b/docs/devices-next/meters/avm-fritzdect.mdx @@ -0,0 +1,69 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..046baec47 --- /dev/null +++ b/docs/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -0,0 +1,144 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solis-hybrid-s` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..fd44bcb70 --- /dev/null +++ b/docs/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `mpm3pm` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/bgetech-ds100.mdx b/docs/devices-next/meters/bgetech-ds100.mdx new file mode 100644 index 000000000..122cfc51e --- /dev/null +++ b/docs/devices-next/meters/bgetech-ds100.mdx @@ -0,0 +1,152 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `bge_tech_ds100` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..a01029eaa --- /dev/null +++ b/docs/devices-next/meters/bgetech-ws100.mdx @@ -0,0 +1,152 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `bge_tech_ws100` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..da5eb214e --- /dev/null +++ b/docs/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..f1b79c028 --- /dev/null +++ b/docs/devices-next/meters/bosswerk-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..e4de29325 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt1xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..c204e6ffd --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em24.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-em24` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..c48f23331 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-em24_e1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..15ed7c16e --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..2723409db --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..0c2ef82c5 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-et112.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt1xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..6e035b568 --- /dev/null +++ b/docs/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..24af96067 --- /dev/null +++ b/docs/devices-next/meters/cfos-powerbrain-meter.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `tcpip` | no | + + + diff --git a/docs/devices-next/meters/demo-battery.mdx b/docs/devices-next/meters/demo-battery.mdx new file mode 100644 index 000000000..2ef01e847 --- /dev/null +++ b/docs/devices-next/meters/demo-battery.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..0616e9504 --- /dev/null +++ b/docs/devices-next/meters/demo-meter.mdx @@ -0,0 +1,123 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..587bb235d --- /dev/null +++ b/docs/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `deye-hybrid-3p` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..470bb7f2d --- /dev/null +++ b/docs/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -0,0 +1,209 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `deye-hybrid-hp3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..0d3b9ce82 --- /dev/null +++ b/docs/devices-next/meters/deye-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..1d1f171df --- /dev/null +++ b/docs/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `deye-storage` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..d96606b1b --- /dev/null +++ b/docs/devices-next/meters/deye-string-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/discovergy.mdx b/docs/devices-next/meters/discovergy.mdx new file mode 100644 index 000000000..33f1e2f2a --- /dev/null +++ b/docs/devices-next/meters/discovergy.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 ID
`meter` | | Beispiel: `1ESY1161229886` | yes | + diff --git a/docs/devices-next/meters/dsmr.mdx b/docs/devices-next/meters/dsmr.mdx new file mode 100644 index 000000000..140b5ead5 --- /dev/null +++ b/docs/devices-next/meters/dsmr.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..907cdd736 --- /dev/null +++ b/docs/devices-next/meters/dzg-dvh4013.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`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 000000000..cf753bab1 --- /dev/null +++ b/docs/devices-next/meters/e3-dc.mdx @@ -0,0 +1,126 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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 | +| 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 new file mode 100644 index 000000000..2d77f6085 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm120-modbus.mdx @@ -0,0 +1,106 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron-sdm120` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..ec04c65f9 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm220-230.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron-sdm220_230` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..6b09c84d7 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm630-modbus.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..293f5c233 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm72d-m.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron-sdm72` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..b1dc23724 --- /dev/null +++ b/docs/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..db1e8ce8b --- /dev/null +++ b/docs/devices-next/meters/enphase-iq-envoy.mdx @@ -0,0 +1,101 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `enphase` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| 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 new file mode 100644 index 000000000..adebe541d --- /dev/null +++ b/docs/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..e1659a5a2 --- /dev/null +++ b/docs/devices-next/meters/esphome-dsmr.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..09e1210fe --- /dev/null +++ b/docs/devices-next/meters/fenecon.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..33a0a378f --- /dev/null +++ b/docs/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `fox-ess-h1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..f1a77c297 --- /dev/null +++ b/docs/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `fox-ess-h3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..f31f72ac7 --- /dev/null +++ b/docs/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `fox-ess-h3-smart` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..26f1b548b --- /dev/null +++ b/docs/devices-next/meters/fronius-ohmpilot.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..c82c53488 --- /dev/null +++ b/docs/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..60ebe4d5f --- /dev/null +++ b/docs/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sunspec-meter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..3f1226139 --- /dev/null +++ b/docs/devices-next/meters/fronius-solar-api-v1.mdx @@ -0,0 +1,112 @@ +--- +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'; +import DeviceFeatures from '@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. + +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! + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..60b75d055 --- /dev/null +++ b/docs/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..5a248084d --- /dev/null +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -0,0 +1,144 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solis-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e6241f14f --- /dev/null +++ b/docs/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -0,0 +1,144 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solis-hybrid-s` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e0a03f694 --- /dev/null +++ b/docs/devices-next/meters/ginlong-solis-inverter.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solis` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..b91abf219 --- /dev/null +++ b/docs/devices-next/meters/go-e-controller.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..4dd75ad40 --- /dev/null +++ b/docs/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -0,0 +1,180 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `goodwe-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..026458125 --- /dev/null +++ b/docs/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..00af33301 --- /dev/null +++ b/docs/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..cc452e4b2 --- /dev/null +++ b/docs/devices-next/meters/growatt-hybrid-inverter.mdx @@ -0,0 +1,180 @@ +--- +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'; +import DeviceFeatures from '@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). +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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `growatt-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..88a03fb3d --- /dev/null +++ b/docs/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -0,0 +1,174 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `growatt-hybrid-tlxh` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..19b7ab86c --- /dev/null +++ b/docs/devices-next/meters/homematic-ip.mdx @@ -0,0 +1,117 @@ +--- +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'; +import DeviceFeatures from '@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 | +| 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
`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 new file mode 100644 index 000000000..8f635e0e3 --- /dev/null +++ b/docs/devices-next/meters/homewizard-kwh-meter.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..d5062e7c6 --- /dev/null +++ b/docs/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..5c9be5cff --- /dev/null +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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)`} /> +
+
+ +
+
+ +## Template Parameter `hoymiles-ahoydtu` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| 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 new file mode 100644 index 000000000..7c439a374 --- /dev/null +++ b/docs/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..aa804313d --- /dev/null +++ b/docs/devices-next/meters/huawei-emma.mdx @@ -0,0 +1,97 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `huawei-emma` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..abc5f557b --- /dev/null +++ b/docs/devices-next/meters/huawei-smartlogger.mdx @@ -0,0 +1,130 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `huawei-smartlogger` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | +| Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | 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 new file mode 100644 index 000000000..4c8c2f8c2 --- /dev/null +++ b/docs/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `huawei-dongle` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e843c2f9c --- /dev/null +++ b/docs/devices-next/meters/huawei-sun2000.mdx @@ -0,0 +1,217 @@ +--- +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'; +import DeviceFeatures from '@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. +See https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `huawei-sun2000` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | +| Timeout
`timeout` | | Standard: `15s`
Beispiel: `10s` | 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 | +| 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 new file mode 100644 index 000000000..2a9d10167 --- /dev/null +++ b/docs/devices-next/meters/iammeter-wem3080.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..cf6392f49 --- /dev/null +++ b/docs/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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/igen-tech-solarman-logger.mdx b/docs/devices-next/meters/igen-tech-solarman-logger.mdx new file mode 100644 index 000000000..117426db6 --- /dev/null +++ b/docs/devices-next/meters/igen-tech-solarman-logger.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..5dd85826d --- /dev/null +++ b/docs/devices-next/meters/index.mdx @@ -0,0 +1,2543 @@ +--- +title: Meters +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; + +# 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 000000000..540458223 --- /dev/null +++ b/docs/devices-next/meters/inepro-pro380-mod.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `inepro` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/iometer.mdx b/docs/devices-next/meters/iometer.mdx new file mode 100644 index 000000000..e47b6c858 --- /dev/null +++ b/docs/devices-next/meters/iometer.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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.mdx b/docs/devices-next/meters/janitza-b-series.mdx new file mode 100644 index 000000000..d7e55d4db --- /dev/null +++ b/docs/devices-next/meters/janitza-b-series.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `janitza` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..af72d1c07 --- /dev/null +++ b/docs/devices-next/meters/janitza-umg-series.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `janitza` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..cc696a968 --- /dev/null +++ b/docs/devices-next/meters/keba-kecontact-e10.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..7d03b92fc --- /dev/null +++ b/docs/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..ee4065b5e --- /dev/null +++ b/docs/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..60a3fbfdf --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-ba.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..a26c42ee0 --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-hybrid.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..1f9685b3d --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-legacy.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..95d1306b3 --- /dev/null +++ b/docs/devices-next/meters/kostal-piko-mp-plus.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/kostal-piko.mdx b/docs/devices-next/meters/kostal-piko.mdx new file mode 100644 index 000000000..a99dda3ac --- /dev/null +++ b/docs/devices-next/meters/kostal-piko.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..67eb3096a --- /dev/null +++ b/docs/devices-next/meters/kostal-plenticore-hybrid-incl-grid-charging-of-the-house-battery.mdx @@ -0,0 +1,107 @@ +--- +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'; +import DeviceFeatures from '@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_!** +_see also https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `kostal-plenticore-gen2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`watchdog` | | Standard: `60s` | no | + 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 000000000..56fc32a2e --- /dev/null +++ b/docs/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -0,0 +1,108 @@ +--- +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'; +import DeviceFeatures from '@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_ + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `kostal-plenticore` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`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 new file mode 100644 index 000000000..1cff62400 --- /dev/null +++ b/docs/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `kostal-ksem-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..067caf6b9 --- /dev/null +++ b/docs/devices-next/meters/kostal-smart-energy-meter.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..30abb9f4e --- /dev/null +++ b/docs/devices-next/meters/lg-ess-home-15.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 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 new file mode 100644 index 000000000..3c71b4b19 --- /dev/null +++ b/docs/devices-next/meters/lg-ess-home-8-10.mdx @@ -0,0 +1,105 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 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 new file mode 100644 index 000000000..a4d091198 --- /dev/null +++ b/docs/devices-next/meters/loxone-miniserver.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..62c81e728 --- /dev/null +++ b/docs/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -0,0 +1,106 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `mtec-eb-gen2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..2a49bc90e --- /dev/null +++ b/docs/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `mtec-eb-gen3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e0d29e62a --- /dev/null +++ b/docs/devices-next/meters/marstek-venus-battery-storage.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `marstek-venus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 | +| 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 new file mode 100644 index 000000000..631725fef --- /dev/null +++ b/docs/devices-next/meters/mhendriks-p1-dongle.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..646e22ca4 --- /dev/null +++ b/docs/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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 | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..992fc8c91 --- /dev/null +++ b/docs/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..cc5b23183 --- /dev/null +++ b/docs/devices-next/meters/my-pv-ac-thor.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + 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 000000000..099259877 --- /dev/null +++ b/docs/devices-next/meters/my-pv-wifi-meter.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/mystrom-switch.mdx b/docs/devices-next/meters/mystrom-switch.mdx new file mode 100644 index 000000000..f0ec9bb24 --- /dev/null +++ b/docs/devices-next/meters/mystrom-switch.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..fd9db58a7 --- /dev/null +++ b/docs/devices-next/meters/openems.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..93f2846ae --- /dev/null +++ b/docs/devices-next/meters/orno-or-we-516.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `orno` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..2b26d673d --- /dev/null +++ b/docs/devices-next/meters/orno-or-we-517.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `orno` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..83b9915c2 --- /dev/null +++ b/docs/devices-next/meters/p1monitor-p1-monitor.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | + diff --git a/docs/devices-next/meters/plexlog.mdx b/docs/devices-next/meters/plexlog.mdx new file mode 100644 index 000000000..dc6537f0f --- /dev/null +++ b/docs/devices-next/meters/plexlog.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `plexlog` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..b84e6c678 --- /dev/null +++ b/docs/devices-next/meters/powerdog.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `powerdog` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `tcpip` | no | + diff --git a/docs/devices-next/meters/powerfox-poweropti.mdx b/docs/devices-next/meters/powerfox-poweropti.mdx new file mode 100644 index 000000000..1648fe5f1 --- /dev/null +++ b/docs/devices-next/meters/powerfox-poweropti.mdx @@ -0,0 +1,78 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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` | 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 new file mode 100644 index 000000000..6124a27a5 --- /dev/null +++ b/docs/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..6219a6f56 --- /dev/null +++ b/docs/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -0,0 +1,210 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..880c3a4f3 --- /dev/null +++ b/docs/devices-next/meters/rct-power.mdx @@ -0,0 +1,99 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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-sbc-ale3.mdx b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx new file mode 100644 index 000000000..615e9b008 --- /dev/null +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sbc-axx3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1698d8570 --- /dev/null +++ b/docs/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sbc-axx3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..6c9037f9e --- /dev/null +++ b/docs/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `saj-h1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..56b768546 --- /dev/null +++ b/docs/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -0,0 +1,155 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `saj-h2` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..c0e7b7f68 --- /dev/null +++ b/docs/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/sax-homespeicher.mdx b/docs/devices-next/meters/sax-homespeicher.mdx new file mode 100644 index 000000000..14faeaaaf --- /dev/null +++ b/docs/devices-next/meters/sax-homespeicher.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..05a667a60 --- /dev/null +++ b/docs/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `schneider-iem3000` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/senec-home.mdx b/docs/devices-next/meters/senec-home.mdx new file mode 100644 index 000000000..6f6fd168f --- /dev/null +++ b/docs/devices-next/meters/senec-home.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `senec-home` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| 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 new file mode 100644 index 000000000..9aa0cdb2b --- /dev/null +++ b/docs/devices-next/meters/senergy-se-4-5-6ktl-s1-g2-inverter.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..bf552975d --- /dev/null +++ b/docs/devices-next/meters/shelly-1pm-mini.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 000000000..4106381fb --- /dev/null +++ b/docs/devices-next/meters/shelly-1pm.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`channel` | | | no | + diff --git a/docs/devices-next/meters/shelly-3em.mdx b/docs/devices-next/meters/shelly-3em.mdx new file mode 100644 index 000000000..0ce521a06 --- /dev/null +++ b/docs/devices-next/meters/shelly-3em.mdx @@ -0,0 +1,93 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..bb9da022b --- /dev/null +++ b/docs/devices-next/meters/shelly-em.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 000000000..72249db1c --- /dev/null +++ b/docs/devices-next/meters/shelly-plug-s.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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-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
`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 000000000..f3e18d033 --- /dev/null +++ b/docs/devices-next/meters/shelly-pm-mini.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 000000000..a7f4ece34 --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-1pm.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`channel` | | | no | + 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 000000000..28b60203e --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-3-em.mdx @@ -0,0 +1,78 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..9f51a8803 --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 000000000..b9ad4e7c2 --- /dev/null +++ b/docs/devices-next/meters/shelly-pro-em.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`channel` | | | no | + diff --git a/docs/devices-next/meters/siemens-7kt1665.mdx b/docs/devices-next/meters/siemens-7kt1665.mdx new file mode 100644 index 000000000..b937eb0d2 --- /dev/null +++ b/docs/devices-next/meters/siemens-7kt1665.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `siemens-7kt1665` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..191d1fc1a --- /dev/null +++ b/docs/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `siemens-junelight` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..ecde93f84 --- /dev/null +++ b/docs/devices-next/meters/siemens-pac-2200.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `siemens-pac2200` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..b8681cc23 --- /dev/null +++ b/docs/devices-next/meters/sigenergy-sigen-hybrid-sigen-pv-max-sigenstore-ec.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sigenergy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | 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 new file mode 100644 index 000000000..9464f7d69 --- /dev/null +++ b/docs/devices-next/meters/sma-data-manager.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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". + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sma-data-manager` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9a624890a --- /dev/null +++ b/docs/devices-next/meters/sma-energy-meter.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..cdb5448c4 --- /dev/null +++ b/docs/devices-next/meters/sma-inverter-speedwire.mdx @@ -0,0 +1,71 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..7c2444e79 --- /dev/null +++ b/docs/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -0,0 +1,98 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sma-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`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 000000000..2188d4795 --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-boy-storage-1-5-2-0-2-5-modbus.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `sma-sbs-15-25-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`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 new file mode 100644 index 000000000..139af3c5a --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-boy-storage-3-7-5-0-6-0-modbus.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `sma-sbs-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`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 new file mode 100644 index 000000000..3c3b4704a --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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-island-modbus.mdx b/docs/devices-next/meters/sma-sunny-island-modbus.mdx new file mode 100644 index 000000000..d5ebe3109 --- /dev/null +++ b/docs/devices-next/meters/sma-sunny-island-modbus.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `sma-si-modbus` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/sma-webbox.mdx b/docs/devices-next/meters/sma-webbox.mdx new file mode 100644 index 000000000..c727c50a1 --- /dev/null +++ b/docs/devices-next/meters/sma-webbox.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..724163824 --- /dev/null +++ b/docs/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..16d5ad962 --- /dev/null +++ b/docs/devices-next/meters/smartfox-box.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..60e2f7910 --- /dev/null +++ b/docs/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..e34f428df --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro-2.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..559bd645e --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro-light-2.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..0c7df080b --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro-light.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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.mdx b/docs/devices-next/meters/smartfox-pro.mdx new file mode 100644 index 000000000..4f33a694d --- /dev/null +++ b/docs/devices-next/meters/smartfox-pro.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..642496556 --- /dev/null +++ b/docs/devices-next/meters/smartfox-reg-extended.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..c5cf199d2 --- /dev/null +++ b/docs/devices-next/meters/smartfox-reg.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..6ed43958e --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e1ae7038d --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..03a48c890 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..f1625b359 --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..11501b72e --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..afdddd98f --- /dev/null +++ b/docs/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar-g3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..6776263cf --- /dev/null +++ b/docs/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -0,0 +1,91 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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/solaredge-hybrid-inverter.mdx b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx new file mode 100644 index 000000000..dd2ee4232 --- /dev/null +++ b/docs/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -0,0 +1,212 @@ +--- +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'; +import DeviceFeatures from '@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". + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solaredge-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`watchdog` | | Standard: `60s` | no | + diff --git a/docs/devices-next/meters/solaredge-inverter.mdx b/docs/devices-next/meters/solaredge-inverter.mdx new file mode 100644 index 000000000..88c359e1d --- /dev/null +++ b/docs/devices-next/meters/solaredge-inverter.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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! + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solaredge-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..4245881d0 --- /dev/null +++ b/docs/devices-next/meters/solarlog.mdx @@ -0,0 +1,67 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..b066dd1c8 --- /dev/null +++ b/docs/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -0,0 +1,126 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solarmax-maxstorage` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`watchdog` | | Standard: `60s` | no | + 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 000000000..a05c6f9d5 --- /dev/null +++ b/docs/devices-next/meters/solarmax-solarmax-smt.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..50f430aa8 --- /dev/null +++ b/docs/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..bd36a9e39 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..5c45838c4 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-energymanager.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..bfe74ca71 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-manager-flex.mdx @@ -0,0 +1,80 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..4d2838b55 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..567e24d32 --- /dev/null +++ b/docs/devices-next/meters/solarwatt-myreserve.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..bb9c9e654 --- /dev/null +++ b/docs/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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`} /> + + + +
+
+ +
+
+ +## 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 000000000..9762186fc --- /dev/null +++ b/docs/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -0,0 +1,210 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `solax` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..68d2064f8 --- /dev/null +++ b/docs/devices-next/meters/solax-inverter-cloud.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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`} /> +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..6cd847049 --- /dev/null +++ b/docs/devices-next/meters/solinteng.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | no | +| Delay
`delay` | | Standard: `100ms` | no | + diff --git a/docs/devices-next/meters/sonnen-comfort.mdx b/docs/devices-next/meters/sonnen-comfort.mdx new file mode 100644 index 000000000..b5381ef9e --- /dev/null +++ b/docs/devices-next/meters/sonnen-comfort.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..1a606993a --- /dev/null +++ b/docs/devices-next/meters/sonnen-eco-5.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..9a25b5caf --- /dev/null +++ b/docs/devices-next/meters/sonnen-eco-6.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..398363002 --- /dev/null +++ b/docs/devices-next/meters/sonnen-oem-6-5.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..903318477 --- /dev/null +++ b/docs/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -0,0 +1,94 @@ +--- +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'; +import DeviceFeatures from '@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. +The power for grid charging can be adapted to the inverter power of the sonnenBatterie via the `maxchargepower` parameter. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sonnenbatterie` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `8080` | 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 new file mode 100644 index 000000000..4bdc46294 --- /dev/null +++ b/docs/devices-next/meters/st-ems.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..37b35c6c2 --- /dev/null +++ b/docs/devices-next/meters/steca-coolcept-flex.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..6b443ec4d --- /dev/null +++ b/docs/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sungrow-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..5f1d8ea4a --- /dev/null +++ b/docs/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -0,0 +1,185 @@ +--- +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'; +import DeviceFeatures from '@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). + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sungrow-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..49f10291f --- /dev/null +++ b/docs/devices-next/meters/sunspec-battery-model-124.mdx @@ -0,0 +1,89 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..b8491464d --- /dev/null +++ b/docs/devices-next/meters/sunspec-battery-model-802.mdx @@ -0,0 +1,91 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..5f56a7889 --- /dev/null +++ b/docs/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -0,0 +1,174 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sunspec-hybrid` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..6c2fb7e12 --- /dev/null +++ b/docs/devices-next/meters/sunspec-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sunspec-inverter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..0f2da8f17 --- /dev/null +++ b/docs/devices-next/meters/sunspec-meter.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sunspec-meter` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..3a58d86e6 --- /dev/null +++ b/docs/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `deye-hybrid-3p` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..f772dfd98 --- /dev/null +++ b/docs/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -0,0 +1,209 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `deye-hybrid-hp3` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..b5d05c904 --- /dev/null +++ b/docs/devices-next/meters/sunsynk-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..5fd8a30c3 --- /dev/null +++ b/docs/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `deye-storage` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e88f30026 --- /dev/null +++ b/docs/devices-next/meters/sunsynk-string-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 Type
`modbus` | | Auswahl: `rs485`, `tcpip` | no | + diff --git a/docs/devices-next/meters/sunway.mdx b/docs/devices-next/meters/sunway.mdx new file mode 100644 index 000000000..1551aa08d --- /dev/null +++ b/docs/devices-next/meters/sunway.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..6b5abc608 --- /dev/null +++ b/docs/devices-next/meters/tasmota-sml-ir-reader-for-smartmeters-e-g-hichi.mdx @@ -0,0 +1,115 @@ +--- +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'; +import DeviceFeatures from '@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 +- **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-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 000000000..5e1dc685b --- /dev/null +++ b/docs/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -0,0 +1,95 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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-three-phase.mdx b/docs/devices-next/meters/tasmota-three-phase.mdx new file mode 100644 index 000000000..e777d9d85 --- /dev/null +++ b/docs/devices-next/meters/tasmota-three-phase.mdx @@ -0,0 +1,93 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..03b2bde32 --- /dev/null +++ b/docs/devices-next/meters/tesla-powerwall.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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. + +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) + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..36a912bee --- /dev/null +++ b/docs/devices-next/meters/tibber-pulse.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `tibber-pulse` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..1312e4ab5 --- /dev/null +++ b/docs/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..e96e18da7 --- /dev/null +++ b/docs/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..ac2678621 --- /dev/null +++ b/docs/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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-em420.mdx b/docs/devices-next/meters/tq-energy-manager-em420.mdx new file mode 100644 index 000000000..aecef83d0 --- /dev/null +++ b/docs/devices-next/meters/tq-energy-manager-em420.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..018722099 --- /dev/null +++ b/docs/devices-next/meters/varta-element.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..c71555cac --- /dev/null +++ b/docs/devices-next/meters/varta-pulse-neo.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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.mdx b/docs/devices-next/meters/varta-pulse.mdx new file mode 100644 index 000000000..fc2a0da40 --- /dev/null +++ b/docs/devices-next/meters/varta-pulse.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..5639bd7e7 --- /dev/null +++ b/docs/devices-next/meters/victron-em24.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-em24` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..680a89776 --- /dev/null +++ b/docs/devices-next/meters/victron-em24_e1.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-em24_e1` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..d5c2d6a24 --- /dev/null +++ b/docs/devices-next/meters/victron-em530-em540.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..d57fcc32b --- /dev/null +++ b/docs/devices-next/meters/victron-energy.mdx @@ -0,0 +1,99 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `victron-energy` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `502` | 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 | +| 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 new file mode 100644 index 000000000..8f1e27bce --- /dev/null +++ b/docs/devices-next/meters/victron-et340.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `cg-emt3xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..041be7169 --- /dev/null +++ b/docs/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `volkszaehler-importexport` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..6ee490ead --- /dev/null +++ b/docs/devices-next/meters/volkszahler-http-api.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `volkszaehler-http` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..c3b2d5b6c --- /dev/null +++ b/docs/devices-next/meters/volkszahler-websocket-api.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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
`uuid` | | | yes | + diff --git a/docs/devices-next/meters/vzlogger.mdx b/docs/devices-next/meters/vzlogger.mdx new file mode 100644 index 000000000..2b8d2dbb0 --- /dev/null +++ b/docs/devices-next/meters/vzlogger.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| IP address or hostname
`host` | | Beispiel: `192.0.2.2` | yes | +| Port
`port` | | Standard: `8081` | no | +| UUID
`uuid` | | | yes | +| Scale factor
`scale` | Multiply by this value | Standard: `1` | 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 new file mode 100644 index 000000000..99c6722d8 --- /dev/null +++ b/docs/devices-next/meters/wago-879-30xx.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `wago-879-30xx` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | + diff --git a/docs/devices-next/meters/wattsonic.mdx b/docs/devices-next/meters/wattsonic.mdx new file mode 100644 index 000000000..d9e5bef6a --- /dev/null +++ b/docs/devices-next/meters/wattsonic.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `wattsonic` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| Modbus Type
`modbus` | | Auswahl: `rs485` | no | +| Battery capacity
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..17f9887c1 --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron-sdm220_230` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..44c8cb21f --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron-sdm220_230` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..4e0bf0a92 --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..4ab0bf3d4 --- /dev/null +++ b/docs/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `eastron` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..3469f9cd2 --- /dev/null +++ b/docs/devices-next/meters/youless-energy-monitor.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..a6590f0c8 --- /dev/null +++ b/docs/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..44661ba0c --- /dev/null +++ b/docs/devices-next/meters/zcs-azzurro-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `sofarsolar` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9295f6fb8 --- /dev/null +++ b/docs/devices-next/meters/zendure-hyper-2000.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Template Parameter `zendure` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..38ac3ab6f --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..0430085b3 --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..b80de19cd --- /dev/null +++ b/docs/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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/tariffs/amber-electric.mdx b/docs/devices-next/tariffs/amber-electric.mdx new file mode 100644 index 000000000..933c2286e --- /dev/null +++ b/docs/devices-next/tariffs/amber-electric.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..052a9a987 --- /dev/null +++ b/docs/devices-next/tariffs/awattar.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..498b9de88 --- /dev/null +++ b/docs/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `electricitymaps` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| URI
`uri` | HTTP(S) address | Beispiel: `https://api-access.electricitymaps.com/2w...1g/` | 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 new file mode 100644 index 000000000..0e58a05ec --- /dev/null +++ b/docs/devices-next/tariffs/electricity-maps-free-api.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `electricitymaps-free` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9f6a32d11 --- /dev/null +++ b/docs/devices-next/tariffs/energinet.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..d660faf03 --- /dev/null +++ b/docs/devices-next/tariffs/enever.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `enever` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`interval` | | Standard: `3h` | no | + diff --git a/docs/devices-next/tariffs/entso-e.mdx b/docs/devices-next/tariffs/entso-e.mdx new file mode 100644 index 000000000..5abbcce5c --- /dev/null +++ b/docs/devices-next/tariffs/entso-e.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `entsoe` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..040753235 --- /dev/null +++ b/docs/devices-next/tariffs/forecast-solar.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`interval` | | Standard: `1h` | no | + diff --git a/docs/devices-next/tariffs/fraunhofer-ise.mdx b/docs/devices-next/tariffs/fraunhofer-ise.mdx new file mode 100644 index 000000000..f4454f1a7 --- /dev/null +++ b/docs/devices-next/tariffs/fraunhofer-ise.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `energy-charts-api` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..6fa914129 --- /dev/null +++ b/docs/devices-next/tariffs/green-grid-compass.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..ec5c64e8b --- /dev/null +++ b/docs/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..52da15194 --- /dev/null +++ b/docs/devices-next/tariffs/grunstromindex.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `grünstromindex` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| ZIP code
`zip` | | | yes | +| Token
`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 new file mode 100644 index 000000000..a57cb00b6 --- /dev/null +++ b/docs/devices-next/tariffs/index.mdx @@ -0,0 +1,277 @@ +--- +title: Tariffs +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; + +# 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 000000000..0fe17a02f --- /dev/null +++ b/docs/devices-next/tariffs/national-grid-eso.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `ngeso` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..34836ad0a --- /dev/null +++ b/docs/devices-next/tariffs/nordpool-spot-prices.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `nordpool` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..7bb107ce1 --- /dev/null +++ b/docs/devices-next/tariffs/octopus-energy-api.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `octopus-api` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e68f6003c --- /dev/null +++ b/docs/devices-next/tariffs/octopus-energy-product-code.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Template Parameter `octopus-productcode` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..5bac053bb --- /dev/null +++ b/docs/devices-next/tariffs/open-meteo.mdx @@ -0,0 +1,76 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`interval` | | Standard: `1h` | no | + diff --git a/docs/devices-next/tariffs/ostrom.mdx b/docs/devices-next/tariffs/ostrom.mdx new file mode 100644 index 000000000..f4085af75 --- /dev/null +++ b/docs/devices-next/tariffs/ostrom.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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/ + + + +
+
+ +
+
+ +## Template Parameter `ostrom` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..cad4ea15e --- /dev/null +++ b/docs/devices-next/tariffs/pun-orario.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..405ec9535 --- /dev/null +++ b/docs/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..08efc85f1 --- /dev/null +++ b/docs/devices-next/tariffs/solcast.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Template Parameter `solcast` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..d8f72e8a5 --- /dev/null +++ b/docs/devices-next/tariffs/spotty-energie.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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 | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..e1ddc5fa2 --- /dev/null +++ b/docs/devices-next/tariffs/tibber.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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/ + + + +
+
+ +
+
+ +## Template Parameter `tibber` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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 new file mode 100644 index 000000000..9ddd62813 --- /dev/null +++ b/docs/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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. + + +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 # 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
`interval` | | Standard: `1h` | no | + diff --git a/docs/devices-next/vehicles/aiways.mdx b/docs/devices-next/vehicles/aiways.mdx new file mode 100644 index 000000000..41f63fd31 --- /dev/null +++ b/docs/devices-next/vehicles/aiways.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..9ffa02e7d --- /dev/null +++ b/docs/devices-next/vehicles/audi.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..80d3096c0 --- /dev/null +++ b/docs/devices-next/vehicles/bmw.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..e9f4d38e9 --- /dev/null +++ b/docs/devices-next/vehicles/citroen.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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]`. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..a6fb48970 --- /dev/null +++ b/docs/devices-next/vehicles/dacia.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..675e1a663 --- /dev/null +++ b/docs/devices-next/vehicles/ds.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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]`. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..a7aec9f8b --- /dev/null +++ b/docs/devices-next/vehicles/evnotify.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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 | +|-----------|-------------|-------|----------| +| 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
`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 | + diff --git a/docs/devices-next/vehicles/fiat.mdx b/docs/devices-next/vehicles/fiat.mdx new file mode 100644 index 000000000..e2ea62a99 --- /dev/null +++ b/docs/devices-next/vehicles/fiat.mdx @@ -0,0 +1,80 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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
`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 | +| 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 new file mode 100644 index 000000000..6228e05fb --- /dev/null +++ b/docs/devices-next/vehicles/ford.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..bcf54e6e4 --- /dev/null +++ b/docs/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | + diff --git a/docs/devices-next/vehicles/hyundai-bluelink.mdx b/docs/devices-next/vehicles/hyundai-bluelink.mdx new file mode 100644 index 000000000..9629cec65 --- /dev/null +++ b/docs/devices-next/vehicles/hyundai-bluelink.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..6497e8b84 --- /dev/null +++ b/docs/devices-next/vehicles/index.mdx @@ -0,0 +1,519 @@ +--- +title: Vehicles +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +import DeviceCard from '@site/src/components/DeviceCard'; +import DeviceGrid from '@site/src/components/DeviceGrid'; + +# Vehicles + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/docs/devices-next/vehicles/iobroker-bmw.mdx b/docs/devices-next/vehicles/iobroker-bmw.mdx new file mode 100644 index 000000000..0b046c024 --- /dev/null +++ b/docs/devices-next/vehicles/iobroker-bmw.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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
`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 | +| 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/iso15118.mdx b/docs/devices-next/vehicles/iso15118.mdx new file mode 100644 index 000000000..1bd1425f9 --- /dev/null +++ b/docs/devices-next/vehicles/iso15118.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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. +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. + + + +
+
+ +
+
+ +## 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
`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 | + diff --git a/docs/devices-next/vehicles/jeep.mdx b/docs/devices-next/vehicles/jeep.mdx new file mode 100644 index 000000000..0c1113bcf --- /dev/null +++ b/docs/devices-next/vehicles/jeep.mdx @@ -0,0 +1,80 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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
`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 | +| 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 new file mode 100644 index 000000000..311b5bc01 --- /dev/null +++ b/docs/devices-next/vehicles/kia-bluelink.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..a798a5e57 --- /dev/null +++ b/docs/devices-next/vehicles/mercedes-benz.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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
`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 | +| 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 new file mode 100644 index 000000000..b35a5980a --- /dev/null +++ b/docs/devices-next/vehicles/mg.mdx @@ -0,0 +1,75 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..3df70f2c7 --- /dev/null +++ b/docs/devices-next/vehicles/mg2mqtt.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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) + + + +
+
+ +
+
+ +## 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
`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 | + diff --git a/docs/devices-next/vehicles/mini.mdx b/docs/devices-next/vehicles/mini.mdx new file mode 100644 index 000000000..613be80d4 --- /dev/null +++ b/docs/devices-next/vehicles/mini.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..be73ba320 --- /dev/null +++ b/docs/devices-next/vehicles/mz2mqtt.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..f12699a47 --- /dev/null +++ b/docs/devices-next/vehicles/nissan-ariya.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..b3e7f0788 --- /dev/null +++ b/docs/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..5250647a3 --- /dev/null +++ b/docs/devices-next/vehicles/nissan-leaf.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..930abf9a2 --- /dev/null +++ b/docs/devices-next/vehicles/niu-e-scooter.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..e79bbe0f2 --- /dev/null +++ b/docs/devices-next/vehicles/opel.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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]`. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..bcb9c6695 --- /dev/null +++ b/docs/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -0,0 +1,78 @@ +--- +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'; +import DeviceFeatures from '@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/). + + + +
+
+ +
+
+ +## 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 | +| 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
`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
`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 new file mode 100644 index 000000000..c98164212 --- /dev/null +++ b/docs/devices-next/vehicles/peugeot.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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]`. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..108c5270a --- /dev/null +++ b/docs/devices-next/vehicles/polestar.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..4cd8054ff --- /dev/null +++ b/docs/devices-next/vehicles/psa-car-controller.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Template Parameter `flobz` + +| Name | Explanation | Value | Optional | +|-----------|-------------|-------|----------| +| 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
`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 | +| 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 new file mode 100644 index 000000000..fc6c8915c --- /dev/null +++ b/docs/devices-next/vehicles/renault.mdx @@ -0,0 +1,75 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..7272fec6e --- /dev/null +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..46f8dcbc5 --- /dev/null +++ b/docs/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..52af19af4 --- /dev/null +++ b/docs/devices-next/vehicles/skoda-enyaq.mdx @@ -0,0 +1,76 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 000000000..23269b35e --- /dev/null +++ b/docs/devices-next/vehicles/smart-1.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..8e59a9ff4 --- /dev/null +++ b/docs/devices-next/vehicles/smart-eq.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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]`. + + + +
+
+ +
+
+ +## 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
`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
`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 | +| 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/tesla-ble.mdx b/docs/devices-next/vehicles/tesla-ble.mdx new file mode 100644 index 000000000..515f423fe --- /dev/null +++ b/docs/devices-next/vehicles/tesla-ble.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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` | 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
`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 | + diff --git a/docs/devices-next/vehicles/tesla.mdx b/docs/devices-next/vehicles/tesla.mdx new file mode 100644 index 000000000..a6a0ff7da --- /dev/null +++ b/docs/devices-next/vehicles/tesla.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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. +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). + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..e956724d3 --- /dev/null +++ b/docs/devices-next/vehicles/teslalogger.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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
`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 | + diff --git a/docs/devices-next/vehicles/teslamate.mdx b/docs/devices-next/vehicles/teslamate.mdx new file mode 100644 index 000000000..800f3aacd --- /dev/null +++ b/docs/devices-next/vehicles/teslamate.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | + diff --git a/docs/devices-next/vehicles/tessie.mdx b/docs/devices-next/vehicles/tessie.mdx new file mode 100644 index 000000000..9e186d245 --- /dev/null +++ b/docs/devices-next/vehicles/tessie.mdx @@ -0,0 +1,71 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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 | + diff --git a/docs/devices-next/vehicles/toyota.mdx b/docs/devices-next/vehicles/toyota.mdx new file mode 100644 index 000000000..e05b136c3 --- /dev/null +++ b/docs/devices-next/vehicles/toyota.mdx @@ -0,0 +1,76 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..51afeae9f --- /dev/null +++ b/docs/devices-next/vehicles/tronity.mdx @@ -0,0 +1,75 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..7221a0518 --- /dev/null +++ b/docs/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -0,0 +1,83 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..431f5eea2 --- /dev/null +++ b/docs/devices-next/vehicles/volvo.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | + diff --git a/docs/devices-next/vehicles/volvo2mqtt.mdx b/docs/devices-next/vehicles/volvo2mqtt.mdx new file mode 100644 index 000000000..c81f318ce --- /dev/null +++ b/docs/devices-next/vehicles/volvo2mqtt.mdx @@ -0,0 +1,71 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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 | + diff --git a/docs/devices-next/vehicles/zero-motorcycles.mdx b/docs/devices-next/vehicles/zero-motorcycles.mdx new file mode 100644 index 000000000..fa76e2a2f --- /dev/null +++ b/docs/devices-next/vehicles/zero-motorcycles.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 d9acd7b6e..ab84c057e 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) @@ -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)`} /> @@ -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: # 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)`} /> + + + + + + + +### 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: # 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)`} /> + + + + + + + +### 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) @@ -244,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)`} /> @@ -262,7 +317,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH4 +### eMH3 (OCPP) @@ -270,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)`} /> @@ -313,7 +368,7 @@ Die "Active load balancing" Lizenz wird benötigt um die Wallbox via Modbus exte -### Eve +### Eve (OCPP) @@ -321,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)`} /> @@ -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 @@ -656,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)`} /> @@ -689,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)`} /> @@ -717,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)`} /> @@ -743,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)`} /> @@ -940,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)`} /> @@ -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 @@ -1460,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)`} /> @@ -1480,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)`} /> @@ -1500,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)`} /> @@ -1520,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)`} /> @@ -1678,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)`} /> @@ -1704,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)`} /> @@ -1730,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)`} /> @@ -1758,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)`} /> @@ -1932,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)`} /> @@ -1960,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)`} /> @@ -2011,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)`} /> @@ -2037,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)`} /> @@ -2155,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)`} /> @@ -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 @@ -2267,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)`} /> @@ -2285,7 +2372,7 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri -## Fronius Wattpilot +## Fronius Wattpilot (OCPP) @@ -2293,17 +2380,88 @@ 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)`} /> + + + + + + + +## 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. + + @@ -2311,7 +2469,7 @@ Das Gerät benötigt eine feste IP Adresse. Es ist wichtig, zuerst EEBus einzuri -## Garo GLB, GLB+, LS4, LS4 compact +### 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) @@ -2364,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)`} /> @@ -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) @@ -2446,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)`} /> @@ -2484,7 +2642,7 @@ In der Go-E App (Menüpunkt "Auto") sollte die Option "Ausstecken simulieren" ak -### Charger V3 +### Charger V3 (OCPP) @@ -2492,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)`} /> @@ -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`} /> @@ -2653,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)`} /> @@ -2681,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)`} /> @@ -2707,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)`} /> @@ -3496,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)`} /> @@ -3526,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)`} /> @@ -3556,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)`} /> @@ -3587,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`} /> @@ -3617,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)`} /> @@ -3780,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)`} /> @@ -4882,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)`} /> @@ -5019,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)`} /> @@ -5071,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 @@ -5079,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)`} /> @@ -5101,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 @@ -5109,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)`} /> @@ -5453,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)`} /> @@ -5470,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)`} /> @@ -5487,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)`} /> @@ -5504,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)`} /> @@ -5602,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)`} /> @@ -5636,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)`} /> @@ -5670,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)`} /> @@ -5704,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)`} /> @@ -5738,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)`} /> @@ -5772,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)`} /> @@ -5806,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)`} /> @@ -5840,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)`} /> @@ -5977,25 +6135,13 @@ Modus "HEMS activated" muss aktiviert sein. RFID-Tags können durch evcc nur gel -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`} /> + template: zaptec + 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)`} /> @@ -6003,17 +6149,29 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- -### Go +### Go (OCPP) +OCPP Native mode + +https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ + + 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: + - 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: # 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)`} /> @@ -6029,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)`} /> @@ -6047,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)`} /> @@ -6065,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)`} /> @@ -6208,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)`} /> @@ -6243,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`} /> @@ -6276,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 @@ -6286,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)`} /> @@ -6304,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)`} /> @@ -6330,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 @@ -6340,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)`} /> @@ -6363,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 @@ -6373,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)`} /> @@ -6391,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)`} /> @@ -6414,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`} /> @@ -6436,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 @@ -6446,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)`} /> @@ -6489,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 @@ -6499,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)`} /> @@ -6537,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)`} /> @@ -6560,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`} /> @@ -6586,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`} /> @@ -6630,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`} /> @@ -6653,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`} /> @@ -6678,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 @@ -6688,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)`} /> @@ -6711,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 @@ -6721,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)`} /> @@ -6746,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 @@ -6756,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)`} /> @@ -6779,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 @@ -6789,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)`} /> @@ -6870,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`} /> @@ -6918,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 @@ -6928,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)`} /> @@ -6951,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 @@ -6961,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)`} /> @@ -6988,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 b4c414e56..2b0005f17 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 fdf4d85d7..bd9311af9 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`} /> @@ -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 @@ -434,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`} /> @@ -513,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`} /> @@ -610,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`} /> @@ -665,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`} /> @@ -1804,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`} /> @@ -1883,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`} /> @@ -2004,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`} /> @@ -2061,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`} /> @@ -2119,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) @@ -2335,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`} /> @@ -2349,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`} /> @@ -2428,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 @@ -2437,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)`} /> @@ -2454,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 @@ -2463,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`} /> @@ -2481,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 @@ -2490,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`} /> @@ -2827,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)`} /> @@ -2847,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)`} /> @@ -2867,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)`} /> @@ -2989,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`} /> @@ -3101,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`} /> @@ -3180,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`} /> @@ -3277,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`} /> @@ -3356,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`} /> @@ -3466,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)`} /> @@ -3567,7 +3578,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 +3590,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 # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -3593,7 +3612,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 # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -3615,7 +3642,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 # Batteriekonfigurations-URI, Firmware Versionen ab 1.36.5-1 erfordern /api/config. [/config, /api/config] (optional)`} /> @@ -3644,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)`} /> @@ -4053,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)`} /> @@ -4084,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 @@ -4108,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`} /> @@ -4140,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 @@ -4164,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`} /> @@ -4615,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)`} /> @@ -4739,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`} /> @@ -4769,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`} /> @@ -4800,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`} /> @@ -4870,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`} /> @@ -4926,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`} /> @@ -4983,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)`} /> @@ -5206,7 +5234,78 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering -## Janitza B series, UMG series +## Janitza + +### B series + + + + + + + + + + + + + + + + + + + + + + +### UMG series @@ -5418,6 +5517,39 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering + + + + + +### Piko + + + + + + + + + + + + + + + + + @@ -5438,6 +5570,39 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering + + +### Piko BA + + + + + + + + + + + + + + + + + + + + ### Piko Hybrid @@ -5506,51 +5671,18 @@ Siehe https://www.iammeter.com/newsshow/net-energy-metering -### Piko, Piko BA +### 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_ - + - - - - - - - - - - - - - - - -### 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_ - - - - - + watchdog: 60s # Watchdog, optional`} /> @@ -5606,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`} /> @@ -5649,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`} /> @@ -5680,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`} /> @@ -5753,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)`} /> @@ -5775,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)`} /> @@ -5797,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)`} /> @@ -5831,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)`} /> @@ -5853,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)`} /> @@ -5875,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)`} /> @@ -6207,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)`} /> @@ -6362,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`} /> @@ -6373,7 +6495,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 @@ -6581,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`} /> @@ -6601,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`} /> @@ -6610,11 +6791,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 +6809,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 +6822,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 +6835,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 +6852,7 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. -## Qcells Q.HOME ESS HYB-G3 +### Q.HOME ESS HYB-G3 @@ -6700,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 @@ -6724,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`} /> @@ -6756,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 @@ -6780,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`} /> @@ -6813,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 @@ -6837,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)`} /> @@ -6867,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)`} /> @@ -6888,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)`} /> @@ -6913,8 +7091,66 @@ 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)`} /> + + + + + + + + +## Saia-Burgess Controls (SBC) + +### ALE3 + + + + + + + + + + + + + + @@ -6923,7 +7159,7 @@ Der QCells Hybrid-Wechselrichter muss in der QCellsCloud angemeldet sein. -## Saia-Burgess Controls ALE3, AWD3 +### AWD3 @@ -7087,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`} /> @@ -7142,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`} /> @@ -7373,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)`} /> @@ -7386,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)`} /> @@ -7399,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`} /> @@ -7783,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`} /> @@ -7797,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`} /> @@ -7811,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`} /> @@ -8006,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`} /> @@ -8042,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`} /> @@ -8075,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`} /> @@ -8129,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`} /> @@ -8219,7 +8405,7 @@ In der Weboberfläche des SMA Data Manager muss im Bereich "Externe Kommunikatio ## Smartfox -### Box, Reg, Reg extended +### Box @@ -8266,7 +8452,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 +8517,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,40 +8529,519 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T + + + + + + + + + + + + + + + + + + + + + + +### Pro 2 + + + +`aux` kann für die Leistung der Warmwasserbereitung verwendet werden. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### 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. + + + + + + + + + + + + + + + + + + + + + + + + + + + +## SofarSolar + +### Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### 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. + + + + + + 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)`} /> @@ -8443,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`} /> @@ -8498,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)`} /> @@ -8565,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)`} /> @@ -8619,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`} /> @@ -8674,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)`} /> @@ -8685,7 +9348,7 @@ Die Verbindung über einen LSE-3 Logger Stick mittels LAN Anschluss und ModBus T -### Inverter, Hybrid Inverter +### Inverter @@ -8864,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)`} /> @@ -8918,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`} /> @@ -8973,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)`} /> @@ -9040,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)`} /> @@ -9094,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`} /> @@ -9149,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)`} /> @@ -9280,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`} /> @@ -9337,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`} /> @@ -9394,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`} /> @@ -9546,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`} /> @@ -9575,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`} /> @@ -9604,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`} /> @@ -9640,22 +10303,73 @@ Für Batteriesteuerung muss über den Solarmax Support die Funktion "Connectivit + template: senergy + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> + + + + + +## Solarwatt + +### EnergyManager + + + + + + + + + + + + + + + + + + + + + - + + -## Solarwatt + -### EnergyManager, EnergyManager Pro +### EnergyManager Pro @@ -9898,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 @@ -9922,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`} /> @@ -9954,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 @@ -9978,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`} /> @@ -10011,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 @@ -10035,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)`} /> @@ -10168,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`} /> @@ -10210,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`} /> @@ -10253,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`} /> @@ -10264,7 +10978,220 @@ Der Solax PV-Wechselrichter muss in der SolaxCloud angemeldet sein. ## Sonnen -### comfort, eco 5, eco 6, oem 6.5 +### comfort + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### eco 5 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### eco 6 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### oem 6.5 @@ -10379,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]`} /> @@ -10440,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`} /> @@ -10482,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`} /> @@ -10525,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`} /> @@ -10824,33 +11751,10 @@ Verbindungen über das WiNet-S-Dongle (WiFi oder LAN) funktionieren nur mit aktu - - - - + + + + port: 502 # Port`} /> @@ -10929,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`} /> @@ -11050,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`} /> @@ -11107,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`} /> @@ -11165,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) @@ -11409,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`} /> @@ -11451,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`} /> @@ -11494,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`} /> @@ -11613,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)`} /> @@ -11638,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)`} /> @@ -11663,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)`} /> @@ -11692,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`} /> @@ -11736,7 +12612,123 @@ Folgende Apps ermöglichen das Erstellen des Tokens: -## VARTA pulse, pulse neo, element +## VARTA + +### element + + + +PV nur verfügbar mit PV-Sensor + + + + + + + + + + + + + + + + + + + + + + + + + + + +### pulse + + + +PV nur verfügbar mit PV-Sensor + + + + + + + + + + + + + + + + + + + + + + + + + + + +### pulse neo @@ -11985,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)`} /> @@ -12014,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`} /> @@ -12215,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`} /> @@ -12257,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`} /> @@ -12300,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`} /> @@ -12574,7 +13555,132 @@ Zur Erfassung der PV-Produktion wird ein extern angebundenener S0-Erzeugungszäh -## ZCS Azzurro Inverter, Hybrid Inverter +## ZCS Azzurro + +### Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Inverter @@ -12709,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`} /> @@ -12724,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`} /> @@ -13348,115 +14454,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 + + + + + + + + + + + + - + -### 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 # Kanal, optional`} /> + + + -#### HTTP API, Import & Export +#### 1PM mini + + + + 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 # Kanal, 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 # Kanal, optional`} /> + + + -### vzlogger +#### EM + + + + + + + + + + + user: # Benutzerkonto, bspw. E-Mail Adresse, User Id, etc. (optional) + password: # Passwort, Bei führenden Nullen bitte in einfache Hochkommata setzen (optional) + channel: 0 # Kanal, optional`} /> - + + -## Schaltbare Steckdosen + -### AVM FritzDECT + + + + + + + +#### Plug S - + + + + + + + + + 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 # Kanal, optional`} /> @@ -13466,12 +14910,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 # Kanal, optional`} /> @@ -13480,7 +14924,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. -### Homematic IP +#### PM mini @@ -13490,75 +14934,96 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. + + + + + + + + channel: 0 # Kanal, optional`} /> - + + + + + + + + + +#### Pro 1PM + + + + + + + + channel: 0 # Kanal, optional`} /> - + + + + + + + + + channel: 0 # Kanal, optional`} /> @@ -13567,19 +15032,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 # Kanal, optional`} /> @@ -13589,9 +15072,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 # Kanal, optional`} /> @@ -13600,7 +15086,7 @@ Zu Demonstrationszwecken. Zähler mit festen Werten. -### Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode +#### Pro EM @@ -13615,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`} /> @@ -13630,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`} /> @@ -13645,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 bbab8f9ec..f6103bbe0 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)`} /> @@ -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 @@ -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,13 +201,13 @@ 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) 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)`} /> @@ -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,16 +270,16 @@ 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) 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)`} /> @@ -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,16 +378,16 @@ 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) 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)`} /> @@ -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,17 +523,17 @@ 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) 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)`} /> @@ -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,13 +830,13 @@ 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) 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)`} /> @@ -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,13 +900,13 @@ 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) 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)`} /> @@ -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,13 +1061,13 @@ 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) 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)`} /> @@ -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) @@ -1250,24 +1250,24 @@ 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`} 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 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) - 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)`} /> @@ -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 87abed220..8961b6121 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 new file mode 100644 index 000000000..eb9c9dced --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac-ocpp.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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 + + +: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: # 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://: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 | +| 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 new file mode 100644 index 000000000..1f5371ad7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abb-terra-ac.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `abb` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..215eac9dd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..c26d12ffb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-single-sbcx.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..f083ad4db --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..03264144e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-em4-twin-sbcx.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..837e50a26 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh1.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..0f04e32c7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..37d2e6df5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh2.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..79d12248e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/abl-emh3-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..24b4cfe48 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..601fc9b83 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alfen-eve.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `alfen` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3a7495458 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alpha-innotec.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..7f2522499 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-ladesaule-twin.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c318efeb5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-mini.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..e0367dec3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/alphatec-wallbox-power.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..62d47649b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-business.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..8c75608b6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-home.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..39133c4bd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-connect-solar.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..f5265b22e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/amperfied-wallbox-energy-control.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..54262686f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-next.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..a3fd11bcc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ampure-unite.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1687e3396 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-plus.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/audi-wallbox-pro.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx new file mode 100644 index 000000000..2bfe5dae2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/audi-wallbox-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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 new file mode 100644 index 000000000..06c2d9180 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-compact.mdx @@ -0,0 +1,69 @@ +--- +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'; +import DeviceFeatures from '@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” +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..5a18a7ec9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autel-ac-maxicharger.mdx @@ -0,0 +1,69 @@ +--- +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'; +import DeviceFeatures from '@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” +* 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..bfa0989dd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-business-wallbox.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..67a4e32a3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/autoaid-intelligent-wallbox.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..4c319ba17 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/avm-fritzdect.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..9d14adc43 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc612.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..431267b7d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-cc613.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..12183c940 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1314.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ed8c7ee32 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bender-icc1324.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..68b06cbfe --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bmw-i-wallbox.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..45a496d4d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-sg-ready.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + +
+
+ +
+
+ +## Templateparameter `emsesp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| 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 new file mode 100644 index 000000000..2ad656474 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/bosch-x-change.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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
`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 000000000..83ed41a5d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20-z.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..77c839a79 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-logamatic-hmc-20.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..e2893fbbe --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/buderus-sg-ready.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + +
+
+ +
+
+ +## Templateparameter `emsesp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| 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 new file mode 100644 index 000000000..611dae2a1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain-solar.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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: +1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) +2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..e5d27d6a7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cfos-power-brain.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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: +1) Start -> Lastmanagement deaktivieren (Modus ist dann Beobachten) +2) Konfiguration -> Hardware -> Phasenumschaltung / Relais 2 (Phasenumschaltung aktivieren) + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..1b2bb2b96 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/charge-amps-halo.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..ad7f78d61 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/compleo-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..4b6965fed --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cta-all-in-one-aeroplus.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..e71db218b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c11e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ad52c7b5f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cubos-c22e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..e856d89e0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..ed5be4e83 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/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 000000000..ddb7369e6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..6de301897 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro-eichrecht-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..e88570a32 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/cupra-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/dadapower-premium-wallbox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx new file mode 100644 index 000000000..46c63557d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/dadapower-premium-wallbox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..d2d17132a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daheimladen-wallbox.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..2c28a0617 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/daikin-homehub-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..78b070701 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-basic.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..523a00eed --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ac-max-smart.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..5f9ad31fc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-slim-charger.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..d954f3b8b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/delta-ultra-fast-charger.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..4e5932969 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/demo-charger.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..bce3f671c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..22e42e4cc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e-on-drive-vbox.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f4ffe5146 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/e3-dc-easy-connect.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..65d31baec --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-core.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..778b21e17 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge-lite.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..3c9d91fa6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-charge.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..718b1ea63 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/easee-home.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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 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 | +| 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 new file mode 100644 index 000000000..c16f20ced --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ebee-wallbox.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2e24f258b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph1.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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 + + +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.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx new file mode 100644 index 000000000..9416ccbb7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cph2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..8ad6ebb78 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/echarge-cpm2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..7286a38a8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ecoharmony-evse-epc-2-0-plus.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..46984c25a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/edgetech-smart-evse.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..8ea63fcc1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eebus-compatible.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..d5155fa92 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elco.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f69af41c0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-biz.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..109ab9457 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-home.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..05226e1ce --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elecq-station.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..5504f1f6c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/eledio-go.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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 + + +: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: # 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://: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 | +| 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 new file mode 100644 index 000000000..ead107c1b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..6ca9a9827 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/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 000000000..a1fb7caa0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..bca5529ee --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro-eichrecht-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..824cf765d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/elli-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/em2go-home.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx new file mode 100644 index 000000000..e70d501b3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-home.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..d831706fd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/em2go-pro-power-ocpp-onc.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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) + + + +
+
+ +
+
+ +## Templateparameter `em2go` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1dfefa8ff --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enercab-smart.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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 + + +: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: # 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://: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 | +| 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 new file mode 100644 index 000000000..3c5e3fc10 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/enplus-ac-ev-charger.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..212b27020 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ensto-chago-wallbox.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f8357f333 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-fix.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..0f87e1b7c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/entratek-power-dot-pro-2.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..f52bb1761 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esl-walli-light.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..887d3a1c6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/esystems-ghostone.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..15b9fe6f0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch-duo.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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. + + +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 new file mode 100644 index 000000000..c9ff10cd4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/etrel-inch.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..de588800e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-elvi.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 # 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 # 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..49fd5c4ad --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evbox-livo.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..d0ed0352e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-din.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..c15af7320 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/evse-wifi.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..759cdc93d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox-move.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..17e10158a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-eprowallbox.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..a1887fcf9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/free2move-esolutions-eprowallbox.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..4f17cd21e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/fronius-wattpilot-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..f75744b73 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glb.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..6c989e106 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-glbplus.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ee53dda14 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4-compact.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..5dc0a36ed --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/garo-ls4.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..59c3e4376 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..908ad2d3f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-gemini.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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". +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-homefix.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx new file mode 100644 index 000000000..79133d2a1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homefix.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..2f20380c6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-homeplus.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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". +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 000000000..ea5824b54 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..78c8d9ec1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-pro.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..6457b1ada --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3-ocpp.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..4edcb0b13 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/go-e-charger-v3.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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". +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/hardy-barth-cph1.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx new file mode 100644 index 000000000..1c224da0f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph1.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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 + + +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 000000000..92822040f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cph2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..6477fc14e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hardy-barth-cpm2.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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/heidelberg-energy-control.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx new file mode 100644 index 000000000..b6c4b2df3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/heidelberg-energy-control.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..57cbc5288 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..8b4f54a6d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/hesotec-esat.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..02023a3ea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/home-assistant-switch.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..b998da226 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homecharge-homecharger.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a90a442f3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homematic-ip.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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
`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
`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 new file mode 100644 index 000000000..cbcc39003 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/homewizard.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..4ba6be806 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-22kt-s0.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..b9ff9d4e4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/huawei-scharger-7ks-s0.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..11c0d694b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/idm.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx new file mode 100644 index 000000000..cd1fe588b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/index.mdx @@ -0,0 +1,3137 @@ +--- +title: Chargers +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +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/chargers/innogy-ebox.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx new file mode 100644 index 000000000..d62ceefb4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/innogy-ebox.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..481426edc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/inro-pantabox.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..f352a34b9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/juice-charger-me.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c39fd8af7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/junkers-sg-ready.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + +
+
+ +
+
+ +## Templateparameter `emsesp` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| 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 new file mode 100644 index 000000000..2343709d0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac20.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..6586d9ae0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac35.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..773d5c1f2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40-e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..5bfd9f86b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac40.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c8b26930b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60-e.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..38cdd5697 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kathrein-kwb-ac60.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `Kathrein` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..e63eab592 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p20.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2c5399424 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-c-series.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..5a98d1863 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p30-x-series.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..100524036 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40-pro.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..0ba22c6ab --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/keba-kecontact-p40.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..23274fc5e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kermi-x-center-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..a3a8ec3ce --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kontron-solar-charger.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..f56aac9e5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kostal-enector.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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. +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 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 new file mode 100644 index 000000000..af15a4eae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/kse-wbx16.mdx @@ -0,0 +1,57 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..ba356d7fb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-evload.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..23801b987 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ladefoxx-mikro-2-0.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..583cc9a1d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lambda-eu-l-series.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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: + +- E-Meter Kommunikationsart: "ModBus Client" +- E-Meter Messpunkt: "Pos. E-Überschuss" + + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..cb0f023a9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/lrt-home-essentialplus.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `alphatec` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..81907f208 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amedio-professional.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2c351bc45 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4business-700.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..451370cf6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-300.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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. +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 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 new file mode 100644 index 000000000..09974dca0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-4you-500.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-icc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ea2022803 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-chargecontrol.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f93732621 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-compact-2-0s.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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. +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 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 new file mode 100644 index 000000000..bc9a6c150 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-premium.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..27f3fd96f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-professional.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1c548c621 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-amtron-xtra.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..dd3274238 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-emobility-gateway-acu.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..f52a873a7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-acu.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a88b835d6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mennekes-smart-t-acu.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a988755ef --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-elwa-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..15ab258d8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor-9s.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..aa49ca04e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/my-pv-ac-thor.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..b614eec0f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/mystrom-switch.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..e1b13f95b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nibe-ap-aw10.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c61b76b31 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/novelan-wpr-net.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ebd7b8002 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-connect.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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) + + + +
+
+ +
+
+ +## Templateparameter `nrgkick-connect` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | 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 new file mode 100644 index 000000000..5ca8c00f2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/nrgkick-gen2.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `nrggen2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..48a7ab3b5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/obo-bettermann-ion.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..bd025239a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ocpp-1-6j-compatible-smart-charging.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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. +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..60430be3b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openevse.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..0fd8043ea --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-pro.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..42f12680f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-series2.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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. + + +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 000000000..e9cd8143e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/openwb-software-2-x.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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: + +* 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 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 new file mode 100644 index 000000000..e5824700e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/optec-mobility-one.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..7b01d523f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/orbis-viaris.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..fd95ea699 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pc-electric-garo.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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! + + + +
+
+ +
+
+ +## 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 000000000..230d02cc2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-business.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `peblar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..17172f085 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home-plus.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `peblar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f12bf248e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/peblar-home.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `peblar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1097a7501 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-charx.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..6eb290ca3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-em-cp-pp-eth.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..52582b42f --- /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,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..282bcb239 --- /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,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..dc8de927d --- /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,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..cee8aba9c --- /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,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..094b35515 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/phoenix-contact-ev-ser.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..fe590d023 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/plugchoice.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + +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. + + + +
+
+ +
+
+ +## Templateparameter `plugchoice` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1845bc012 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-connect.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..fa42b0a52 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-mobile-charger-plus.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..181772c78 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/porsche-wallbox.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..5f74c8411 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-alpha-xt.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Typ
`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 new file mode 100644 index 000000000..f3e6e61ec --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-mono-xt.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Typ
`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 new file mode 100644 index 000000000..24dbd62a0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-pni.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Typ
`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-xtplus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx new file mode 100644 index 000000000..32dd5f358 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pracht-xtplus.mdx @@ -0,0 +1,90 @@ +--- +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'; +import DeviceFeatures from '@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 Typ
`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 new file mode 100644 index 000000000..e51557cf6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsares-simplebox.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..58e63bf78 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/pulsatrix.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..580571965 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/qcells-q-home-edrive-a.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f9951fa2f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoaura.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1604e9c81 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/roth-thermoterra.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..bdaff220b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schneider-evlink-pro.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..71f98529d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/schrack-i-charge-cion.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..43a43b771 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro-s.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..a4ab52f84 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/senec-wallbox-pro.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..c988c8221 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-1.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 | +| 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 | +| 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 000000000..db1945a94 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plug-s.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 | +| 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 | +| 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 000000000..1768ac53a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-plus-1.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 | +| 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 | +| 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 000000000..bd7135b5d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/shelly-pro-1.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 | +| 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 | +| 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/siemens-versicharge-gen3.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx new file mode 100644 index 000000000..91ad3d4d3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/siemens-versicharge-gen3.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `versicharge` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..12528ddee --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-connect.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..9025ad820 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro-eichrecht.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..540fc43b4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..fe1b5d181 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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 000000000..3e1b8b148 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/skoda-iv-charger-connectplus.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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 000000000..17985f4e1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-echarger.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx new file mode 100644 index 000000000..662b76d06 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sma-ev-charger.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..43a0a3562 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartfox-pro-charger.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..42ef60dfa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/smartwb.mdx @@ -0,0 +1,43 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..4824eddc1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solaredge-home-ev-charger.mdx @@ -0,0 +1,64 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `keba-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3c8a4558a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/solax-x3-evc.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2cf9ec38e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sonnen-sonnencharger.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..8d9274a81 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/spelsberg-wallbox-smart-pro.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..8b25b9873 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stark-in-strom-easy.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..9105ad609 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-lwa-lwz-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..eb778a3ae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/stiebel-eltron-wpm-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..3266b46b8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e-01.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..e31f80da3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac011e.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..7cfdc6fc8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/sungrow-ac22e-01.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..33a81207e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tasmota-single-phase.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..d48157ae7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tecalor-thz-sg-ready.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..dd6186a95 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/technisat-technivolt.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..dcdb3c996 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tesla-wall-connector-gen-3.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..87ffb87cd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tessie.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `tessie` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Fahrzeugidentifikationsnummer
`vin` | Wenn mehrere Fahrzeuge eines Herstellers vorhanden sind | Beispiel: `W...` | ja | +| Tessie API Token
`token` | | | 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 new file mode 100644 index 000000000..3f140e474 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tigo-go-ev-charger.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..446907c2a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-pro.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..c4018251b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp-charger-smart.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..a9b9a2d1a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-pro.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..06d858ead --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tinkerforge-warp3-charger-smart.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..cad9d3689 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..679ed312f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..1757e89a1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/ubitricity-heinz.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..d15970fac --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/v2c-trydan.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..1d0ffb8cd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vaillant-sensonet-sg-ready.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..f051dc337 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-connect-plus.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..9ab23cfd0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/vestel-evc04-home-smart.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f3472bd55 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station-via-gx.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `victron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2e1cc34d8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/victron-ev-charging-station.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `victron-evcs` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..4f5467e4a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viessmann-heatpump-sg-ready.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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. + + + 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`} /> +
+
+ +
+
+ +## 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...
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 new file mode 100644 index 000000000..0082269c9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/viridian-ev-evse-epc-2-0-plus.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..d276258cb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-connect-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..f7afb03d9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..2b7747ca8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-charger-pro-eichrecht-2.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + +Die Nutzung der Phasenumschaltung ist in evcc momentan noch nicht möglich. + +Eine Identifikation des Fahrzeugs über die RFID Karte ist nicht möglich. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..c64e14e3d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-connect.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/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 000000000..98a40ec3b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volkswagen-id-charger-pro.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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). + +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/volt-time-one.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx new file mode 100644 index 000000000..b11761305 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-one.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..849b89e1e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c21696c61 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source-2s.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..54453eae3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/volt-time-source.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `volttime` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1e6cd3e13 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco-2-0-s.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..52cfa4196 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-eco.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..79fb8894b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbe-pro.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `phoenix-ev-eth` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..98a9f5b96 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..aecf9a8c1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-commander-2.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..6fcc70a1a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..c6f6ac59b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-copper-sb.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..f483a66d6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..508ed9ca2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-max.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..0b03bdafa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus-fw-5-x.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..7bd989ba8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wallbox-pulsar-plus.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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/ + +* “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: # 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://: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 | +| 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 new file mode 100644 index 000000000..2f5587ecb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/walther-werke-basic-evo-pro.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `heidelberg` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..d784fdef0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-live.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `bender-cc` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ada8617af --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-next.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..26f9fead8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/webasto-unite.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `vestel` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ebbdf8893 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/weidmuller-ac-smart.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..76e1706c9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bwl.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1e82a3cdd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/wolf-bws.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `luxtronik` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..a32e8869f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-2.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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
`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 000000000..0a6627bf3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go-ocpp.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 + +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: # 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://: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 | +| 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 new file mode 100644 index 000000000..a832c480c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-go.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..efcd62721 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zaptec-pro.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..f5bd6ffe3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zewotherm-eu-l-series.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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: + +- E-Meter Kommunikationsart: "ModBus Client" +- E-Meter Messpunkt: "Pos. E-Überschuss" + + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..0091e8f6f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/chargers/zj-beny-bcp-ev-charger.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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: + - 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: # 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://: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 | +| 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 new file mode 100644 index 000000000..76b45b485 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/a-tronix.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..59b2e85a3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a43.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..bf0388cab --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-a44.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..4f4760d36 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b23.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..bfd9e147b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/abb-b24.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `abb-ab` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..54bcb3ce6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/acrel-adw300.mdx @@ -0,0 +1,124 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `acrel-adw300` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..5bb1a8fd6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ads-tec-storaxe.mdx @@ -0,0 +1,61 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..ec2baf652 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/alpha-ess-storion-smile.mdx @@ -0,0 +1,181 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `alpha-ess-smile` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 000000000..ed01b8e14 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ampere-ampere-storagepro.mdx @@ -0,0 +1,155 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `saj-h2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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/anker-micro-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx new file mode 100644 index 000000000..a8642085b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/anker-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..cc0236fd5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/apsystems-ez1.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..ad427f531 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/avm-fritzdect.mdx @@ -0,0 +1,69 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..2a91809bf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/axitec-axihycon-12-15h.mdx @@ -0,0 +1,144 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solis-hybrid-s` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..b5067f5c7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bernecker-engineering-mpm3pm.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `mpm3pm` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..6b41657ed --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ds100.mdx @@ -0,0 +1,152 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `bge_tech_ds100` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..19b89ee72 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bgetech-ws100.mdx @@ -0,0 +1,152 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `bge_tech_ws100` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c827f45f6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosch-bpt-s-5-hybrid.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..4d16d6d32 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/bosswerk-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..919e000ff --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em110-111-112.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt1xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..38b45a080 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-em24` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c004cce03 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em24_e1.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-em24_e1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..91491b50a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em330-em340.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..353232615 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-em530-em540.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..bbca817e8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et112.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt1xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..7d5810e1f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/carlo-gavazzi-et330-et340.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..5556fb201 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/cfos-powerbrain-meter.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..01ec5183b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-battery.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..1e6ace29a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/demo-meter.mdx @@ -0,0 +1,123 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..26ee75ee1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-3p-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `deye-hybrid-3p` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..fb8ac9b25 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-hp3-hybrid-inverter.mdx @@ -0,0 +1,209 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `deye-hybrid-hp3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..63e8a5203 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..c853ebf94 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-storage-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `deye-storage` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3934cbc98 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/deye-string-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..3dd7dc579 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/discovergy.mdx @@ -0,0 +1,66 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..a53a34d56 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dsmr.mdx @@ -0,0 +1,54 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..9976bc5ce --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/dzg-dvh4013.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..6bd6b8c39 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/e3-dc.mdx @@ -0,0 +1,126 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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 | +| 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 new file mode 100644 index 000000000..a1922d6ee --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm120-modbus.mdx @@ -0,0 +1,106 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron-sdm120` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..88923abc6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm220-230.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron-sdm220_230` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..d9bdce1c0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm630-modbus.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2e6b8c0c1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72d-m.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron-sdm72` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..6435ebecc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/eastron-sdm72dm-v2.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..16004ea6f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/enphase-iq-envoy.mdx @@ -0,0 +1,101 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `enphase` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| 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 new file mode 100644 index 000000000..cc4da1400 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dlms-meter-austria.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..6f30b1dc0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/esphome-dsmr.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..5dd584c45 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fenecon.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..062582bc2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h1-series-hybrid-inverter.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `fox-ess-h1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3d3627214 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-series-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `fox-ess-h3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..448c23716 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/foxess-h3-smart-series-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `fox-ess-h3-smart` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..d32081492 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-ohmpilot.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..229a29ede --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-primo-gen24-plus.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..d9799027c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-smartmeter-via-inverter.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sunspec-meter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..70777942b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-solar-api-v1.mdx @@ -0,0 +1,112 @@ +--- +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'; +import DeviceFeatures from '@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. + +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! + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..49b0d0b04 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/fronius-symo-gen24-plus.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..46019fd29 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-rhi-series.mdx @@ -0,0 +1,144 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solis-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1cae979d9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-hybrid-inverter-s-series.mdx @@ -0,0 +1,144 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solis-hybrid-s` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..e76cef2c6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/ginlong-solis-inverter.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solis` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..0a44de418 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/go-e-controller.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..66c9cc58f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-et-eh-bh-bt-hybrid-inverter.mdx @@ -0,0 +1,180 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `goodwe-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..f33914b63 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-goodwe-over-wifi.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..3b04863aa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/goodwe-sdt-dt-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..384fdd916 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-hybrid-inverter.mdx @@ -0,0 +1,180 @@ +--- +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'; +import DeviceFeatures from '@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. +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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `growatt-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2cb58c4ca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/growatt-tl-x-h-hybrid-inverter.mdx @@ -0,0 +1,174 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `growatt-hybrid-tlxh` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..90d31a4fa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homematic-ip.mdx @@ -0,0 +1,117 @@ +--- +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'; +import DeviceFeatures from '@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 | +| 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
`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 new file mode 100644 index 000000000..fc80d8300 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-kwh-meter.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..5f8b01cca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/homewizard-wi-fi-p1-meter.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..7c8507fd2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-ahoydtu.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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)`} /> +
+
+ +
+
+ +## Templateparameter `hoymiles-ahoydtu` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| 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 new file mode 100644 index 000000000..ab0bc7e82 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/hoymiles-hm-and-hms-series-via-opendtu.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..cae7caf8d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-emma.mdx @@ -0,0 +1,97 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `huawei-emma` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..e0a499974 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-smartlogger.mdx @@ -0,0 +1,130 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `huawei-smartlogger` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Modbus Typ
`modbus` | | Auswahl: `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | 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 new file mode 100644 index 000000000..653fc8a65 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000-sdongle.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `huawei-dongle` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..63fbbb19b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/huawei-sun2000.mdx @@ -0,0 +1,217 @@ +--- +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'; +import DeviceFeatures from '@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. +Siehe https://forum.huawei.com/enterprise/en/modbus-tcp-guide/thread/667250677153415168-667213868771979264 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `huawei-sun2000` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Modbus Typ
`modbus` | | Auswahl: `rs485`, `tcpip` | nein | +| Zeitüberschreitung
`timeout` | | Standard: `15s`
Beispiel: `10s` | 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 | +| 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 new file mode 100644 index 000000000..ca0a3661b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..cd046625d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iammeter-wem3080t-wem3046t-wem3050t.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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/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 000000000..9d08e2608 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/igen-tech-solarman-logger.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..fdc9f6751 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/index.mdx @@ -0,0 +1,2543 @@ +--- +title: Meters +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +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/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 000000000..132ebada9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/inepro-pro380-mod.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `inepro` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..b174c9ba3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/iometer.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx new file mode 100644 index 000000000..38c808ea9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-b-series.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `janitza` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..736f30097 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/janitza-umg-series.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `janitza` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..fa7be6d12 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/keba-kecontact-e10.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..ac2d3be65 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-c-kem-c.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..29d765354 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-energy-meter-p-kem-p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..b7cf46a56 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-ba.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..57a4c7706 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-hybrid.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..076504422 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-legacy.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..202b35774 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko-mp-plus.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx new file mode 100644 index 000000000..c277017d6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-piko.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..0501f5683 --- /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,107 @@ +--- +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'; +import DeviceFeatures from '@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_!** +_siehe auch https://github.com/evcc-io/evcc/wiki/Kostal-Plenticore_ + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `kostal-plenticore-gen2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 new file mode 100644 index 000000000..b8c3c7eb5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-plenticore-hybrid.mdx @@ -0,0 +1,108 @@ +--- +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'; +import DeviceFeatures from '@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_ + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `kostal-plenticore` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 new file mode 100644 index 000000000..f1f771078 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter-via-inverter.mdx @@ -0,0 +1,52 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `kostal-ksem-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..a5fbcb405 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/kostal-smart-energy-meter.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..051d3e261 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-15.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..9318ce573 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/lg-ess-home-8-10.mdx @@ -0,0 +1,105 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..5db72ef60 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/loxone-miniserver.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..6df440ce7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen2.mdx @@ -0,0 +1,106 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `mtec-eb-gen2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..6a0861c61 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/m-tec-energy-butler-gen3.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `mtec-eb-gen3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..81184e052 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/marstek-venus-battery-storage.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `marstek-venus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 | +| 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 new file mode 100644 index 000000000..4d8d03be5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mhendriks-p1-dongle.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..0b0597822 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-2.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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 | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2c77d05e2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-elwa-e.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..359f89c11 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-ac-thor.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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-wifi-meter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx new file mode 100644 index 000000000..de52195d7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/my-pv-wifi-meter.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..757bdc0cc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/mystrom-switch.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..8338c9dca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/openems.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..6da6de773 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-516.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `orno` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ee26596ef --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/orno-or-we-517.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `orno` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..31be98c14 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/p1monitor-p1-monitor.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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/plexlog.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx new file mode 100644 index 000000000..320c72839 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/plexlog.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `plexlog` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..da3ad73ad --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerdog.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `powerdog` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..98a7a4625 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/powerfox-poweropti.mdx @@ -0,0 +1,78 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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` | 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 new file mode 100644 index 000000000..af16c39e9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-hybrid-inverter-cloud.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..c17681866 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/qcells-q-home-ess-hyb-g3.mdx @@ -0,0 +1,210 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..6a49f5b5c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/rct-power.mdx @@ -0,0 +1,99 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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-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 000000000..f379ea16c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-ale3.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sbc-axx3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3b4163d16 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saia-burgess-controls-sbc-awd3.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sbc-axx3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..0681500a2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h1-series-hybrid-solar-inverter.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `saj-h1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..fdda5a668 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-h2-series-hybrid-solar-inverter.mdx @@ -0,0 +1,155 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `saj-h2` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..26a95df6b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/saj-r5-series-solar-inverter.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..a6069badd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sax-homespeicher.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..168b25ed4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/schneider-electric-iem3xxx-modbus.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `schneider-iem3000` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..57aff49fc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/senec-home.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `senec-home` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| 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 new file mode 100644 index 000000000..2e8924e9a --- /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,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..5a351a323 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm-mini.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..c632d4377 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-1pm.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..57fa1dd0b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-3em.mdx @@ -0,0 +1,93 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..ef8a756c9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-em.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..f0362f87d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-plug-s.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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-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 | +| 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 new file mode 100644 index 000000000..73432a903 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pm-mini.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..17a182452 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-1pm.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..a4e1ad841 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3-em.mdx @@ -0,0 +1,78 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..11a5ff157 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-3em-monophase-mode.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..d504634bd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/shelly-pro-em.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..5417f0681 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-7kt1665.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `siemens-7kt1665` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..9d09f09d1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-junelight-smart-battery.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `siemens-junelight` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..d3dbf703d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/siemens-pac-2200.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `siemens-pac2200` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..6236a86d2 --- /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,90 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sigenergy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | 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 new file mode 100644 index 000000000..24a3504f8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-data-manager.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sma-data-manager` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3e52aad7f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-energy-meter.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..ed3b127eb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-inverter-speedwire.mdx @@ -0,0 +1,71 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..97611dff8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-smart-energy-hybrid-inverter.mdx @@ -0,0 +1,98 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sma-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 000000000..e42d35d25 --- /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,65 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `sma-sbs-15-25-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 new file mode 100644 index 000000000..2b2ed4b71 --- /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,65 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `sma-sbs-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 new file mode 100644 index 000000000..094ac3dce --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-home-manager-2-0.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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-island-modbus.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx new file mode 100644 index 000000000..970cc4bcd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-sunny-island-modbus.mdx @@ -0,0 +1,65 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `sma-si-modbus` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 new file mode 100644 index 000000000..4aaffd07a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-webbox.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..d48b4f3fa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sma-wechselrichter-modbus.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..e3ca69095 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-box.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..f59eba1eb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-light-em2-firmware.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..fe8c9d5d9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-2.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..26d3273c5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light-2.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..f87d04923 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro-light.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx new file mode 100644 index 000000000..c95240d5d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-pro.mdx @@ -0,0 +1,92 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..a7dfcab75 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg-extended.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..44f02487e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/smartfox-reg.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..70f1467ba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c3bc503af --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-3-6k-ep.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..5451ae32f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-hyd-5-20k-3ph.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..4491e7538 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..bcf3b4710 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-5-24ktl-g3.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2476e1ea6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sofarsolar-sofar-80-136ktl.mdx @@ -0,0 +1,206 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar-g3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..0af4b0002 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaranzeige-solaranzeige.mdx @@ -0,0 +1,91 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## 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/solaredge-hybrid-inverter.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx new file mode 100644 index 000000000..840bbb252 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-hybrid-inverter.mdx @@ -0,0 +1,212 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solaredge-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 new file mode 100644 index 000000000..bafd87d12 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solaredge-inverter.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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! + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solaredge-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c7f51d12b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarlog.mdx @@ -0,0 +1,67 @@ +--- +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'; +import DeviceFeatures from '@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! + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..2355dfde1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-max-storage-max-storage-ultimate.mdx @@ -0,0 +1,126 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solarmax-maxstorage` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 new file mode 100644 index 000000000..24351b66a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-solarmax-smt.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..cea7dac46 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarmax-sp-series-inverter.mdx @@ -0,0 +1,49 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..855729cba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager-pro.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..0425bc1d9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-energymanager.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..5ca755697 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-manager-flex.mdx @@ -0,0 +1,80 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..18fa6998b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve-matrix-lan-oder-powergateway.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..c77461d4f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solarwatt-myreserve.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..08df19eb8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-inverter-cloud.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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`} /> + + + +
+
+ +
+
+ +## 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 000000000..9cbef9c38 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-hybrid-x1-x3-g3-g4.mdx @@ -0,0 +1,210 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `solax` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..99032fe89 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solax-inverter-cloud.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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. + +**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`} /> +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..2c56eada0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/solinteng.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..6b731b3ae --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-comfort.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..1fa601c75 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-5.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..3346326c8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-eco-6.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..2330b8bc3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-oem-6-5.mdx @@ -0,0 +1,100 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..7c35431e1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sonnen-sonnenbatterie.mdx @@ -0,0 +1,94 @@ +--- +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'; +import DeviceFeatures from '@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. +Die Leistung für das Netzladen kann an die Wechselrichterleistung der sonnenBatterie über den Parameter `maxchargepower` angepasst werden. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sonnenbatterie` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `8080` | 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 new file mode 100644 index 000000000..51b1ddd3d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/st-ems.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..6a045107c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/steca-coolcept-flex.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..d97063113 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sg-series-inverter.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sungrow-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3f110b9a0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sungrow-sh-series-hybrid-inverter.mdx @@ -0,0 +1,185 @@ +--- +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'; +import DeviceFeatures from '@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). + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sungrow-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..cd851c45d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-124.mdx @@ -0,0 +1,89 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..2083087a7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-battery-model-802.mdx @@ -0,0 +1,91 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..da2285b41 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-hybrid-inverter.mdx @@ -0,0 +1,174 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sunspec-hybrid` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2e2b60567 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sunspec-inverter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..8c5c9dccb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunspec-meter.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sunspec-meter` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..991708923 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-3p-hybrid-inverter.mdx @@ -0,0 +1,178 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `deye-hybrid-3p` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..3664f6e33 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-hp3-hybrid-inverter.mdx @@ -0,0 +1,209 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `deye-hybrid-hp3` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..99d0ed6a2 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-micro-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..a9d8d877a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-storage-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `deye-storage` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..b0bf99225 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunsynk-string-inverter.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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 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 new file mode 100644 index 000000000..f0a3b0eaa --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/sunway.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..d0c243f36 --- /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,115 @@ +--- +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'; +import DeviceFeatures from '@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 +- **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-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 000000000..13890a244 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-tasmota-1-phase-plus-sml-meter.mdx @@ -0,0 +1,95 @@ +--- +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'; +import DeviceFeatures from '@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) + +
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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-three-phase.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx new file mode 100644 index 000000000..4ad402cd5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tasmota-three-phase.mdx @@ -0,0 +1,93 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..09e80e593 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tesla-powerwall.mdx @@ -0,0 +1,102 @@ +--- +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'; +import DeviceFeatures from '@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. + +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) + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..83e8be0da --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tibber-pulse.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `tibber-pulse` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..2c164b292 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-h-series-smart-plug.mdx @@ -0,0 +1,44 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..6d8f726ff --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tp-link-tapo-p-series-smart-plug.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..2896091e9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em2xx-em3xx.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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-em420.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx new file mode 100644 index 000000000..e3edc6d94 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/tq-energy-manager-em420.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 000000000..45212338a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-element.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..549c0f274 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse-neo.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx new file mode 100644 index 000000000..7c38abc18 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/varta-pulse.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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 + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..78424500e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-em24` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..b3c996686 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em24_e1.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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/) + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-em24_e1` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..bbe16c47d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-em530-em540.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..09af053a3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-energy.mdx @@ -0,0 +1,99 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `victron-energy` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `502` | 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 | +| 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 new file mode 100644 index 000000000..57b2a06f0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/victron-et340.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `cg-emt3xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..173cf8e33 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api-import-and-export.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `volkszaehler-importexport` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..a2246beaf --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-http-api.mdx @@ -0,0 +1,46 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `volkszaehler-http` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..fbb51ebef --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/volkszahler-websocket-api.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## 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
`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 new file mode 100644 index 000000000..2c2159444 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/vzlogger.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| IP-Adresse oder Hostname
`host` | | Beispiel: `192.0.2.2` | ja | +| Port
`port` | | Standard: `8081` | nein | +| UUID
`uuid` | | | ja | +| Skalierungsfaktor
`scale` | Multipliziere Rohwert mit diesem Faktor | Standard: `1` | 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 new file mode 100644 index 000000000..b64b2fe2c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wago-879-30xx.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `wago-879-30xx` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..074436e35 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/wattsonic.mdx @@ -0,0 +1,163 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `wattsonic` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Modbus Typ
`modbus` | | Auswahl: `rs485` | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | 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 new file mode 100644 index 000000000..3a1675619 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em110-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron-sdm220_230` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c72505c0f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em111-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron-sdm220_230` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..c68b746f4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em120-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..01b59ca1b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/weidmuller-em122-rtu-2p.mdx @@ -0,0 +1,84 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `eastron` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..def028904 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/youless-energy-monitor.mdx @@ -0,0 +1,63 @@ +--- +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'; +import DeviceFeatures from '@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. + + + + + + + + + + + + + + +
+
+ +
+
+ +## 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 000000000..f30dbfe21 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-hybrid-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..4dc9e9b17 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zcs-azzurro-inverter.mdx @@ -0,0 +1,149 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `sofarsolar` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..883696c12 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zendure-hyper-2000.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + + + + + + + + + + + + +
+
+ +
+
+ +## Templateparameter `zendure` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..d4cde9ecc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-in-luxembourg.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..51c4d6110 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus-v2.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 000000000..79e84aaa5 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/meters/zuidwijk-slimmelezer-plus.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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/tariffs/amber-electric.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx new file mode 100644 index 000000000..3b81be7b8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/amber-electric.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..fc4209204 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/awattar.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..e9f2933dd --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-commercial-api.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `electricitymaps` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| URI
`uri` | HTTP(S) Adresse | Beispiel: `https://api-access.electricitymaps.com/2w...1g/` | 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 new file mode 100644 index 000000000..cc1a4f138 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/electricity-maps-free-api.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `electricitymaps-free` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1f2874d2b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/energinet.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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
`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 new file mode 100644 index 000000000..74876e532 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/enever.mdx @@ -0,0 +1,58 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `enever` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 | +| 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 new file mode 100644 index 000000000..0bd2d7459 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/entso-e.mdx @@ -0,0 +1,60 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `entsoe` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..3cd03044e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/forecast-solar.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..223daac2f --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/fraunhofer-ise.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `energy-charts-api` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..9ca2e03f1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/green-grid-compass.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..6fe6023b0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/groupe-e-vario-plus.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..e6cb8c002 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/grunstromindex.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `grünstromindex` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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/index.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx new file mode 100644 index 000000000..8a501750d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/index.mdx @@ -0,0 +1,277 @@ +--- +title: Tariffs +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +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/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 000000000..590d9a9f4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/national-grid-eso.mdx @@ -0,0 +1,45 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `ngeso` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..46d69a3d3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/nordpool-spot-prices.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `nordpool` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1d58ebc26 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-api.mdx @@ -0,0 +1,48 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `octopus-api` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..ca73db5c3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/octopus-energy-product-code.mdx @@ -0,0 +1,47 @@ +--- +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'; +import DeviceFeatures from '@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 + +
+
+ + + +
+
+ +
+
+ +## Templateparameter `octopus-productcode` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..b31e79351 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/open-meteo.mdx @@ -0,0 +1,76 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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 new file mode 100644 index 000000000..d3c2658e0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/ostrom.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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/ + + + +
+
+ +
+
+ +## Templateparameter `ostrom` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..1612e05a8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/pun-orario.mdx @@ -0,0 +1,53 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 new file mode 100644 index 000000000..c47492d5a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/smartenergy-smartcontrol.mdx @@ -0,0 +1,50 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..022871ccc --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/solcast.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## Templateparameter `solcast` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..59dcf4db7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/spotty-energie.mdx @@ -0,0 +1,56 @@ +--- +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'; +import DeviceFeatures from '@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 | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..bb9c3fa84 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/tibber.mdx @@ -0,0 +1,59 @@ +--- +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'; +import DeviceFeatures from '@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/ + + + +
+
+ +
+
+ +## Templateparameter `tibber` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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 new file mode 100644 index 000000000..11769a532 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/tariffs/victron-vrm-solar-forecast.mdx @@ -0,0 +1,55 @@ +--- +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'; +import DeviceFeatures from '@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. + + +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 # 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 | +| 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 new file mode 100644 index 000000000..7a2b4da2e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/aiways.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..ecfb244ba --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/audi.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..3b821d2db --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/bmw.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..d13082667 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/citroen.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..3dac52151 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/dacia.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..b113ed707 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ds.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..0569d0307 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/evnotify.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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 | +|-----------|-----------|------|----------| +| 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
`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 | + 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 000000000..cae1ff8b0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/fiat.mdx @@ -0,0 +1,80 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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
`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 | +| 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 new file mode 100644 index 000000000..0be69439b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/ford.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..d2cd74579 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/generic-vehicle-without-api.mdx @@ -0,0 +1,62 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | + 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 000000000..63c2afa4b --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/hyundai-bluelink.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..3842ed404 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/index.mdx @@ -0,0 +1,519 @@ +--- +title: Vehicles +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +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/vehicles/iobroker-bmw.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx new file mode 100644 index 000000000..95d13a13d --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iobroker-bmw.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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
`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 | +| 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/iso15118.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx new file mode 100644 index 000000000..0c7daac57 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/iso15118.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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. +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. + + + +
+
+ +
+
+ +## 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
`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 | + 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 000000000..c23b5c61e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/jeep.mdx @@ -0,0 +1,80 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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
`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 | +| 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 new file mode 100644 index 000000000..5218bc372 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/kia-bluelink.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..b652e223a --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mercedes-benz.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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
`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 | +| 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 new file mode 100644 index 000000000..d72171ea4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg.mdx @@ -0,0 +1,75 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..4b971de09 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mg2mqtt.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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) + + + +
+
+ +
+
+ +## 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
`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 | + 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 000000000..4c893894e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mini.mdx @@ -0,0 +1,85 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..dbb53448e --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/mz2mqtt.mdx @@ -0,0 +1,70 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..f66a39979 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-ariya.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..4e2762f78 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf-pre-2019.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..e103f01a6 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/nissan-leaf.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..33d64e8ab --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/niu-e-scooter.mdx @@ -0,0 +1,51 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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 new file mode 100644 index 000000000..5daa42913 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/opel.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..c9778bb24 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/open-vehicle-monitoring-system.mdx @@ -0,0 +1,78 @@ +--- +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'; +import DeviceFeatures from '@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/). + + + +
+
+ +
+
+ +## 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 | +| 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
`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
`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 new file mode 100644 index 000000000..60854d718 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/peugeot.mdx @@ -0,0 +1,79 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | +| 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 new file mode 100644 index 000000000..c83d15363 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/polestar.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..a7761b45c --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/psa-car-controller.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## Templateparameter `flobz` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| 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
`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 | +| 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 new file mode 100644 index 000000000..d16af0eca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/renault.mdx @@ -0,0 +1,75 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..1437306a0 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen3-ateca-leon-formentor-tarraco.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..35b6e8555 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/seat-cupraconnect-gen4-born-formentor-tavascan.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..8851140a3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/skoda-enyaq.mdx @@ -0,0 +1,76 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 000000000..dd190b378 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-1.mdx @@ -0,0 +1,77 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..1c108a1c8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/smart-eq.mdx @@ -0,0 +1,82 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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
`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 | +| 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/tesla-ble.mdx b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx new file mode 100644 index 000000000..7f8469763 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla-ble.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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` | 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
`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 | + 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 000000000..1e38cea00 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tesla.mdx @@ -0,0 +1,96 @@ +--- +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'; +import DeviceFeatures from '@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. +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). + + + +
+
+ +
+
+ +## Templateparameter `tesla` + +| Name | Erklärung | Wert | Optional | +|-----------|-----------|------|----------| +| Titel
`title` | Wird in der Benutzeroberfläche angezeigt | | nein | +| Akkukapazität
`capacity` | | Beispiel: `50`
Einheit: kWh | nein | +| 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
`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 | +| 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 new file mode 100644 index 000000000..77ec7aadb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslalogger.mdx @@ -0,0 +1,74 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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
`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 | + 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 000000000..79f1636e1 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/teslamate.mdx @@ -0,0 +1,68 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | + 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 000000000..94ad95fc4 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tessie.mdx @@ -0,0 +1,71 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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 | + 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 000000000..4f259f9f3 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/toyota.mdx @@ -0,0 +1,76 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..c22daacb7 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/tronity.mdx @@ -0,0 +1,75 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 new file mode 100644 index 000000000..84dfa62c8 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volkswagen-we-connect-id.mdx @@ -0,0 +1,83 @@ +--- +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'; +import DeviceFeatures from '@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 + + + +
+
+ +
+
+ +## 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
`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 | +| 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 new file mode 100644 index 000000000..c65a3d4ca --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo.mdx @@ -0,0 +1,87 @@ +--- +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'; +import DeviceFeatures from '@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. +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. + + + +
+
+ +
+
+ +## 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 | +| 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
`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 | + 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 000000000..4b84951fb --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/volvo2mqtt.mdx @@ -0,0 +1,71 @@ +--- +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'; +import DeviceFeatures from '@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. + + + +
+
+ +
+
+ +## 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
`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 | + 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 000000000..167eff1e9 --- /dev/null +++ b/i18n/de/docusaurus-plugin-content-docs/current/devices-next/vehicles/zero-motorcycles.mdx @@ -0,0 +1,73 @@ +--- +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'; +import DeviceFeatures from '@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` + +| 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
`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 | +| 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 e0b48a782..bab24f2b6 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) @@ -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)`} /> @@ -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: # 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)`} /> + + + + + + + +### 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: # 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)`} /> + + + + + + + +### 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) @@ -245,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)`} /> @@ -263,7 +318,7 @@ https://library.e.abb.com/public/8f07987a3a284da6bf4e4f8f53cd6502/ABB_Terra_AC_C -### eMH4 +### eMH3 (OCPP) @@ -271,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)`} /> @@ -314,7 +369,7 @@ The "Active load balancing" license is required for external Modbus control of t -### Eve +### Eve (OCPP) @@ -322,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)`} /> @@ -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 @@ -657,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)`} /> @@ -690,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)`} /> @@ -718,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)`} /> @@ -744,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)`} /> @@ -941,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)`} /> @@ -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 @@ -1461,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)`} /> @@ -1481,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)`} /> @@ -1501,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)`} /> @@ -1521,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)`} /> @@ -1679,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)`} /> @@ -1705,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)`} /> @@ -1731,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)`} /> @@ -1759,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)`} /> @@ -1933,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)`} /> @@ -1961,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)`} /> @@ -2012,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)`} /> @@ -2038,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)`} /> @@ -2156,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)`} /> @@ -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 @@ -2268,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)`} /> @@ -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) @@ -2294,17 +2381,88 @@ 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)`} /> + + + + + + + +## 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. + + @@ -2312,7 +2470,7 @@ The device requires a fixed IP addres. It's important to set up EEBus first. Aft -## Garo GLB, GLB+, LS4, LS4 compact +### LS4 compact @@ -2357,7 +2515,7 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" -### Charger Gemini +### Charger Gemini (OCPP) @@ -2365,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)`} /> @@ -2439,7 +2597,7 @@ Requires firmware 040.0 or later. HTTP API v1 or v2 must be activated. -### Charger PRO +### Charger PRO (OCPP) @@ -2447,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)`} /> @@ -2485,7 +2643,7 @@ The “simulate unplugging” option should be activated in the Go-E app ("Car" -### Charger V3 +### Charger V3 (OCPP) @@ -2493,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)`} /> @@ -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`} /> @@ -2654,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)`} /> @@ -2682,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)`} /> @@ -2708,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)`} /> @@ -3497,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)`} /> @@ -3527,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)`} /> @@ -3557,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)`} /> @@ -3588,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`} /> @@ -3618,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)`} /> @@ -3781,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)`} /> @@ -4883,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)`} /> @@ -5020,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)`} /> @@ -5072,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 @@ -5080,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)`} /> @@ -5102,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 @@ -5110,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)`} /> @@ -5456,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)`} /> @@ -5473,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)`} /> @@ -5490,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)`} /> @@ -5507,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)`} /> @@ -5605,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)`} /> @@ -5639,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)`} /> @@ -5673,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)`} /> @@ -5707,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)`} /> @@ -5741,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)`} /> @@ -5775,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)`} /> @@ -5809,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)`} /> @@ -5843,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)`} /> @@ -5980,25 +6138,13 @@ Mode "HEMS activated" must be enabled. RFID tags can only be read by evcc. -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: zaptec + 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)`} /> @@ -6006,17 +6152,29 @@ https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native- -### Go +### Go (OCPP) +OCPP Native mode + +https://help.zaptec.com/hc/en-001/articles/22330328601489-Zaptec-Go-OCPP-Native-configuration-guide#h_01HP261F5NP6Z9VY0MVHJCZEBJ + + 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: + - 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: # 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)`} /> @@ -6032,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)`} /> @@ -6050,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)`} /> @@ -6068,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)`} /> @@ -6210,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)`} /> @@ -6245,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`} /> @@ -6278,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 @@ -6288,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)`} /> @@ -6306,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)`} /> @@ -6332,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 @@ -6342,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)`} /> @@ -6365,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 @@ -6375,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)`} /> @@ -6393,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)`} /> @@ -6416,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`} /> @@ -6438,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 @@ -6448,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)`} /> @@ -6491,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 @@ -6501,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)`} /> @@ -6539,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)`} /> @@ -6562,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`} /> @@ -6588,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`} /> @@ -6632,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`} /> @@ -6655,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`} /> @@ -6680,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 @@ -6690,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)`} /> @@ -6713,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 @@ -6723,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)`} /> @@ -6748,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 @@ -6758,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)`} /> @@ -6781,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 @@ -6791,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)`} /> @@ -6872,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`} /> @@ -6920,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 @@ -6930,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)`} /> @@ -6953,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 @@ -6963,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)`} /> @@ -6990,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 bbd05e2cf..cd5a5fcaa 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 5e643cdad..b0fcb303b 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`} /> @@ -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 @@ -435,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`} /> @@ -514,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`} /> @@ -611,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`} /> @@ -666,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`} /> @@ -1805,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`} /> @@ -1884,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`} /> @@ -2005,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`} /> @@ -2062,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`} /> @@ -2120,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) @@ -2336,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`} /> @@ -2350,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`} /> @@ -2429,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 @@ -2438,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)`} /> @@ -2455,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 @@ -2464,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`} /> @@ -2482,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 @@ -2491,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`} /> @@ -2828,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)`} /> @@ -2848,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)`} /> @@ -2868,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)`} /> @@ -2990,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`} /> @@ -3102,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`} /> @@ -3181,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`} /> @@ -3278,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`} /> @@ -3357,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`} /> @@ -3467,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)`} /> @@ -3568,7 +3579,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 +3591,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 # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -3594,7 +3613,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 # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -3616,7 +3643,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 # Battery configuration URI, Firmware starting with 1.36.5-1 requires /api/config. [/config, /api/config] (optional)`} /> @@ -3645,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)`} /> @@ -4054,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)`} /> @@ -4085,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 @@ -4109,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`} /> @@ -4141,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 @@ -4165,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`} /> @@ -4616,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)`} /> @@ -4740,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`} /> @@ -4770,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`} /> @@ -4801,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`} /> @@ -4871,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`} /> @@ -4927,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`} /> @@ -4984,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)`} /> @@ -5207,7 +5235,78 @@ See https://www.iammeter.com/newsshow/net-energy-metering -## Janitza B series, UMG series +## Janitza + +### B series + + + + + + + + + + + + + + + + + + + + + + +### UMG series @@ -5419,6 +5518,39 @@ See https://www.iammeter.com/newsshow/net-energy-metering + + + + + +### Piko + + + + + + + + + + + + + + + + + @@ -5439,6 +5571,39 @@ See https://www.iammeter.com/newsshow/net-energy-metering + + +### Piko BA + + + + + + + + + + + + + + + + + + + + ### Piko Hybrid @@ -5507,51 +5672,18 @@ See https://www.iammeter.com/newsshow/net-energy-metering -### Piko, Piko BA +### 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_ - + - - - - - - - - - - - - - - - -### 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_ - - - - - + watchdog: 60s # Watchdog, optional`} /> @@ -5607,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`} /> @@ -5650,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`} /> @@ -5681,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`} /> @@ -5754,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)`} /> @@ -5776,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)`} /> @@ -5798,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)`} /> @@ -5832,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)`} /> @@ -5854,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)`} /> @@ -5876,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)`} /> @@ -6208,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)`} /> @@ -6363,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`} /> @@ -6374,7 +6496,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 @@ -6582,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`} /> @@ -6602,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`} /> @@ -6611,11 +6792,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 +6810,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 +6823,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 +6836,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 +6853,7 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. -## Qcells Q.HOME ESS HYB-G3 +### Q.HOME ESS HYB-G3 @@ -6701,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 @@ -6725,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`} /> @@ -6757,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 @@ -6781,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`} /> @@ -6814,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 @@ -6838,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)`} /> @@ -6868,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)`} /> @@ -6889,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)`} /> @@ -6914,8 +7092,66 @@ 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)`} /> + + + + + + + + +## Saia-Burgess Controls (SBC) + +### ALE3 + + + + + + + + + + + + + + @@ -6924,7 +7160,7 @@ The QCells hybrid inverter has to be registered in the QCellsCloud. -## Saia-Burgess Controls ALE3, AWD3 +### AWD3 @@ -7088,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`} /> @@ -7143,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`} /> @@ -7374,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)`} /> @@ -7387,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)`} /> @@ -7400,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`} /> @@ -7784,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`} /> @@ -7798,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`} /> @@ -7812,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`} /> @@ -8049,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`} /> @@ -8085,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`} /> @@ -8118,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`} /> @@ -8172,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`} /> @@ -8220,7 +8406,7 @@ In the web interface of the SMA Data Manager you need to activate "Modbus Server ## Smartfox -### Box, Reg, Reg extended +### Box @@ -8267,7 +8453,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 +8518,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,40 +8530,519 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th + + + + + + + + + + + + + + + + + + + + + + +### Pro 2 + + + +`aux` can be used for water heating power. + + + + + + + + + + + + + + + + + + + + + + + + + + + +### 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. + + + + + + + + + + + + + + + + + + + + + + + + + + + +## SofarSolar + +### Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### 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. + + + + + + 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)`} /> @@ -8444,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`} /> @@ -8499,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)`} /> @@ -8566,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)`} /> @@ -8620,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`} /> @@ -8675,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)`} /> @@ -8686,7 +9349,7 @@ LSE-3 logger stick using a LAN connection and ModBus TCP via the port 8899 is th -### Inverter, Hybrid Inverter +### Inverter @@ -8865,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)`} /> @@ -8919,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`} /> @@ -8974,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)`} /> @@ -9041,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)`} /> @@ -9095,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`} /> @@ -9150,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)`} /> @@ -9281,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`} /> @@ -9338,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`} /> @@ -9395,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`} /> @@ -9547,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`} /> @@ -9576,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`} /> @@ -9605,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`} /> @@ -9641,22 +10304,73 @@ For batter control, the "Connectivity+" function must be activated via the Solar + template: senergy + usage: pv + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port`} /> + + + + + +## Solarwatt + +### EnergyManager + + + + + + + + + + + + + + + + + + + + + - + + -## Solarwatt + -### EnergyManager, EnergyManager Pro +### EnergyManager Pro @@ -9899,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 @@ -9923,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`} /> @@ -9955,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 @@ -9979,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`} /> @@ -10012,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 @@ -10036,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)`} /> @@ -10169,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`} /> @@ -10211,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`} /> @@ -10254,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`} /> @@ -10265,7 +10979,220 @@ The Solax inverter has to be registered in the SolaxCloud. ## Sonnen -### comfort, eco 5, eco 6, oem 6.5 +### comfort + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### eco 5 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### eco 6 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### oem 6.5 @@ -10380,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]`} /> @@ -10441,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`} /> @@ -10483,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`} /> @@ -10526,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`} /> @@ -10826,32 +11753,9 @@ Connections via the WiNet-S dongle (WiFi or LAN) only work with the latest firmw - - - + + + port: 502 # Port`} /> @@ -10930,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`} /> @@ -11051,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`} /> @@ -11108,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`} /> @@ -11166,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) @@ -11410,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`} /> @@ -11452,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`} /> @@ -11495,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`} /> @@ -11614,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)`} /> @@ -11639,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)`} /> @@ -11664,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)`} /> @@ -11693,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`} /> @@ -11737,7 +12613,123 @@ The following apps allow to create the token: -## VARTA pulse, pulse neo, element +## VARTA + +### element + + + +PV only available with PV sensor + + + + + + + + + + + + + + + + + + + + + + + + + + + +### pulse + + + +PV only available with PV sensor + + + + + + + + + + + + + + + + + + + + + + + + + + + +### pulse neo @@ -11986,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)`} /> @@ -12015,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`} /> @@ -12216,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`} /> @@ -12258,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`} /> @@ -12301,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`} /> @@ -12575,7 +13556,132 @@ An externally connected S0 generation meter is required to record the solar prod -## ZCS Azzurro Inverter, Hybrid Inverter +## ZCS Azzurro + +### Hybrid Inverter + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### Inverter @@ -12710,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`} /> @@ -12725,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`} /> @@ -13349,115 +14455,453 @@ For demonstration purposes. Meter with a fixed set of values. - + + + + +### Volkszähler + +#### HTTP API + + + + + + + + + +#### HTTP API, Import & Export + + + + + + + + + +#### WebSocket API + + + + + + + + + +### vzlogger + + + + + + + + + +## Switchable sockets + +### AVM FritzDECT + + + + + + + + + + + + + + + + + + + + + + +### Homematic IP + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +### myStrom Switch + + + + + + + + + + + + + + + + + + + + + + +### Shelly + +#### 1PM + + + + + + + + + + + + - + -### 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 # Channel, optional`} /> + + + -#### HTTP API, Import & Export +#### 1PM mini + + + + 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 # Channel, 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 # Channel, optional`} /> + + + -### vzlogger +#### EM + + + + + + + + + + + user: # Username, e.g. email address, user id, etc. (optional) + password: # Password, Use single quotes in case of leading zeros (optional) + channel: 0 # Channel, optional`} /> - + + -## Switchable sockets + -### AVM FritzDECT + + + + + + + +#### Plug S - + + + + + + + + + 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 # Channel, optional`} /> @@ -13467,12 +14911,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 # Channel, optional`} /> @@ -13481,7 +14925,7 @@ For demonstration purposes. Meter with a fixed set of values. -### Homematic IP +#### PM mini @@ -13491,75 +14935,96 @@ For demonstration purposes. Meter with a fixed set of values. + + + + + + + + channel: 0 # Channel, optional`} /> - + + + + + + + + + +#### Pro 1PM + + + + + + + + channel: 0 # Channel, optional`} /> - + + + + + + + + + channel: 0 # Channel, optional`} /> @@ -13568,19 +15033,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 # Channel, optional`} /> @@ -13590,9 +15073,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 # Channel, optional`} /> @@ -13601,7 +15087,7 @@ For demonstration purposes. Meter with a fixed set of values. -### Shelly 1PM, EM, Plug S, Pro 3EM in monophase mode +#### Pro EM @@ -13616,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`} /> @@ -13631,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`} /> @@ -13646,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 7a87644ed..55dad2551 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)`} /> @@ -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 @@ -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,13 +204,13 @@ 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) 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)`} /> @@ -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,16 +273,16 @@ 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) 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)`} /> @@ -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,16 +381,16 @@ 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) 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)`} /> @@ -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,17 +526,17 @@ 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) 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)`} /> @@ -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,13 +833,13 @@ 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) 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)`} /> @@ -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,13 +903,13 @@ 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) 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)`} /> @@ -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,13 +1065,13 @@ 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) 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)`} /> @@ -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) @@ -1254,24 +1254,24 @@ 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, 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: 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, 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) 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)`} /> @@ -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 1ef10730a..f05ba53be 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 9ef53cc19..36292fa36 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.11", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -23,12 +24,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 +4097,440 @@ "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/@evcc/icons": { + "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" + } + }, "node_modules/@hapi/hoek": { "version": "9.3.0", "resolved": "https://registry.npmjs.org/@hapi/hoek/-/hoek-9.3.0.tgz", @@ -6457,12 +6898,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 +6946,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 +10819,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", @@ -11383,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", @@ -11461,6 +11966,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 +23019,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 +23761,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 +24587,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 +24676,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 +24709,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 c7a60cb7e..d23e99ee1 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", @@ -24,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.11", "clsx": "^2.0.0", "docusaurus-plugin-generate-llms-txt": "^0.0.1", "file-loader": "^6.2.0", @@ -34,6 +37,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 +54,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 9df9b834e..70c047fea 100644 --- a/sidebars.js +++ b/sidebars.js @@ -11,16 +11,5 @@ 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'], - }, - ], - */ + sidebar: [{ type: "autogenerated", dirName: "." }], }; diff --git a/src/components/DeviceCard.module.css b/src/components/DeviceCard.module.css new file mode 100644 index 000000000..c12ee7ee2 --- /dev/null +++ b/src/components/DeviceCard.module.css @@ -0,0 +1,149 @@ +.deviceCard { + background: var(--ifm-card-background-color); + border: 2px solid var(--ifm-color-emphasis-300); + border-radius: 12px; + cursor: pointer; + overflow: hidden; + height: 100%; + display: flex; + flex-direction: column; +} + +.deviceCard:hover { + border-color: #22c55e; +} + +.deviceCard:focus-visible { + outline: 2px solid #22c55e; + outline-offset: 2px; +} + +.thumbnailContainer { + position: relative; + width: 100%; + aspect-ratio: 1; + background: #ffffff; + border-bottom: 1px solid var(--ifm-color-emphasis-300); + display: flex; + align-items: center; + justify-content: center; + overflow: hidden; +} + +.thumbnail { + width: 100%; + height: 100%; + object-fit: contain; +} + +.content { + padding: 16px; + flex: 1; + display: flex; + flex-direction: column; + gap: 4px; +} + +.title { + font-size: 1.1rem; + font-weight: 400; + color: var(--ifm-color-emphasis-900); + line-height: 1.4; +} + +.capabilities { + display: flex; + flex-wrap: wrap; + gap: 6px; + margin-top: 16px; +} + +.capabilityTag { + 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; +} + +.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: 400; + font-size: 0.875rem; +} + +.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-fit, minmax(200px, 1fr)); + gap: 24px; + margin: 32px 0; +} + +/* Large screens - more columns with auto-fit */ +@media (min-width: 1400px) { + :global(.device-grid) { + gap: 24px; + } +} + +/* Medium screens - 3 columns */ +@media (max-width: 1200px) { + :global(.device-grid) { + gap: 20px; + } +} + +/* Small screens - 2 columns */ +@media (max-width: 768px) { + :global(.device-grid) { + gap: 16px; + } + + .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 { + 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 000000000..932e9d497 --- /dev/null +++ b/src/components/DeviceCard.tsx @@ -0,0 +1,98 @@ +import React from "react"; +import "@evcc/icons"; +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; + group?: string; + type: string; + name: string; +} + +const DeviceCard: React.FC = ({ + brand, + description, + thumbnail, + capabilities = [], + requirements = [], + href, + group, + type, + name, +}) => { + 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 &&
{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/components/DeviceGrid.tsx b/src/components/DeviceGrid.tsx new file mode 100644 index 000000000..814d865bc --- /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 000000000..143734da3 --- /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 000000000..198a24721 --- /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/css/custom.css b/src/css/custom.css index 24908ab51..85f3b55ab 100644 --- a/src/css/custom.css +++ b/src/css/custom.css @@ -147,3 +147,67 @@ 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; +} + +/* 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; + } +} + +.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 new file mode 100644 index 000000000..c9af5278f --- /dev/null +++ b/src/generateDevicesNext.ts @@ -0,0 +1,545 @@ +import * as fs from "fs"; +import * as path from "path"; +import * as yaml from "js-yaml"; +import * as countries from "i18n-iso-countries"; + +// 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; + 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; + advanced?: string; + }>; +} + +interface DeviceCard { + id: string; + brand: string; + description: string; + thumbnail: string; + capabilities: string[]; + requirements: string[]; + countries: string[]; + identifier: string; + group?: 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", + "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 = { + "tab.grid": "Grid", + "tab.pv": "PV", + "tab.battery": "Battery", + "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 { + _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 indentCode = (code: string, list = false): string => { + 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(/^/, " - "); + 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 || ""; + const description = data.product.description || ""; + const identifier = data.product.identifier; + + // Skip if no identifier is provided + if (!identifier) { + console.warn( + `No identifier found for template: ${data._filename} - skipping`, + ); + return null; + } + + return { + id: `${brand}-${description}`.replace(/\s+/g, "-").toLowerCase(), + brand, + description, + thumbnail: `/img/devices/${deviceType}/${identifier}.jpg`, + capabilities: data.capabilities || [], + requirements: data.requirements || [], + countries: data.countries || [], + identifier, + group: data.product.group, + }; +}; + +const generateOverviewPage = ( + cards: DeviceCard[], + deviceType: string, + language: string, +): string => { + const title = deviceType.charAt(0).toUpperCase() + deviceType.slice(1) + "s"; + + return `--- +title: ${title} +hide_table_of_contents: true +sidebar_class_name: sidebar-item-no-expand +--- + +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}`), + ) + .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.identifier}" + group="${card.group || ""}" + type="${deviceType}" + name="${card.identifier}" + />`; + }) + .join("\n")} + +`; +}; + +const escapeMarkdown = (text: string): string => { + return text.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, + 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); + const title = titleParts.join(" ").trim() || "Device"; + + // Generate custom edit URL pointing to the original template + 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 +sidebar_class_name: sidebar-item-hidden +--- + +import DeviceConfig from '@site/src/components/DeviceConfig'; +import DeviceFeatures from '@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} +
+
+ +
+
+ +${parameterTable ? parameterTable + "\n\n" : ""}${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.identifier}.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 000000000..8684120d0 --- /dev/null +++ b/static/img/devices/placeholder.svg @@ -0,0 +1,6 @@ + + + + + + \ No newline at end of file diff --git a/templates/release/de/charger/Kathrein_0.yaml b/templates/release/de/charger/Kathrein_0.yaml deleted file mode 100644 index d955ccb70..000000000 --- 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 2746ca56c..000000000 --- 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 b6166e984..000000000 --- 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 ca7f52614..000000000 --- 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 49a865ed5..000000000 --- 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 58bc15d24..000000000 --- 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 000000000..602477d9b --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..381783931 --- /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: Modbus Typ + 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 b5713aa39..000000000 --- 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 000000000..202b76005 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..d048ff07c --- /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: Modbus Typ + 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 000000000..98123d835 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..18ca90ea7 --- /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: Modbus Typ + 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 e4a7c746b..000000000 --- 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 000000000..a043baad3 --- /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: Modbus Typ + 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 000000000..42ffa1578 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..07d7cb384 --- /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: Modbus Typ + 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 000000000..5684f9146 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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_0.yaml b/templates/release/de/charger/abl_0.yaml deleted file mode 100644 index 2db141ddc..000000000 --- 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 fe121664f..000000000 --- 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 b2d358efb..000000000 --- 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 0761b5620..000000000 --- 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 3bee385fb..000000000 --- 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 6c3e454ae..000000000 --- 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 000000000..904ee1f45 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..a2d42f98c --- /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: Modbus Typ + 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 dab2234bb..000000000 --- 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 000000000..d9dd3942f --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..518aa009f --- /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: Modbus Typ + 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 000000000..5e8d5c613 --- /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: Modbus Typ + 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 000000000..46b124e31 --- /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: Modbus Typ + 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 f36678851..000000000 --- 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 63b255a2f..000000000 --- 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 ac6c3362e..000000000 --- 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 3b9d09a6e..000000000 --- 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 3a2dc3806..000000000 --- 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 000000000..ac680333a --- /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: Modbus Typ + 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 000000000..1257080b9 --- /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: Modbus Typ + 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 000000000..432df8690 --- /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: Modbus Typ + 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 000000000..a2a2ddbb2 --- /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: Modbus Typ + 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 98a6dd4e9..000000000 --- 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 630984a20..000000000 --- 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 000000000..3ad807978 --- /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 000000000..70bb45cd6 --- /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: Modbus Typ + 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 000000000..ee49cf9af --- /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 000000000..5556ffdc8 --- /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 000000000..cccb19782 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..46c2289f0 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..aa094ab87 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..6410310b3 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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/avm-fritzdect.yaml b/templates/release/de/charger/avm-fritzdect.yaml new file mode 100644 index 000000000..467f55391 --- /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 000000000..147ab2527 --- /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: Modbus Typ + 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 000000000..9e57f070d --- /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: Modbus Typ + 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 417e1e4f4..000000000 --- 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 c953ec2b7..000000000 --- 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 bc12f6cbf..000000000 --- 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 b13449765..000000000 --- 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 17d1f30ad..000000000 --- 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 ff9f0b1a4..000000000 --- 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 8f1e78128..000000000 --- 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 eb69b8adf..000000000 --- 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 a96a8bb27..000000000 --- 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 d775fa375..000000000 --- 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 e6c46fb51..000000000 --- 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 2d1787be6..000000000 --- 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 664f9d82d..000000000 --- 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 3a86e05e4..000000000 --- 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 4f28a641c..000000000 --- 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 3931ee686..000000000 --- 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 000000000..2690aef08 --- /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: Modbus Typ + 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 000000000..76b72a554 --- /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: Modbus Typ + 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 190d28e58..000000000 --- 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 31eed1568..000000000 --- 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 56fd24702..000000000 --- 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 bbb7bf6a4..000000000 --- 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 000000000..06bbd1e79 --- /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: Modbus Typ + 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 000000000..031cebdd0 --- /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: # 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: Token + 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 000000000..1cddf2d75 --- /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 # Watchdog, 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: 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 new file mode 100644 index 000000000..a78a37256 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..411823aea --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..e23e2b651 --- /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: # 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: Token + 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 000000000..9fd6477e8 --- /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 000000000..c71a98028 --- /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 163f712d3..000000000 --- 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 4f14aadc3..000000000 --- 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 000000000..2b5c8cc7e --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..7c42c83ad --- /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: Modbus Typ + 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 000000000..d0857a9d4 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..6c2c11de6 --- /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: Modbus Typ + 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 000000000..4f1c2cf82 --- /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: Modbus Typ + 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 000000000..af0a32d24 --- /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 000000000..e6c9cfd3c --- /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 000000000..333a5b16d --- /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 000000000..b6fd01cab --- /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 000000000..de1c86b22 --- /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 000000000..ca29f5276 --- /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: Modbus Typ + 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 7a916c80e..000000000 --- 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 670421035..000000000 --- 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 000000000..753c0e884 --- /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 000000000..ca3ce7dfb --- /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: Modbus Typ + 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 94e598bf3..000000000 --- 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 000000000..8ffd1c540 --- /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: Modbus Typ + 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 000000000..8193f11c5 --- /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: Modbus Typ + 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 000000000..58925a414 --- /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: Modbus Typ + 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 000000000..c76440831 --- /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: Modbus Typ + 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 03b583921..000000000 --- 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 d1e9371bf..000000000 --- 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 87a93af3d..000000000 --- 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 effcd7f08..000000000 --- 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 000000000..3bc95d1c8 --- /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 b72e91f48..000000000 --- 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 000000000..e7d33aeb2 --- /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: Modbus Typ + 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 000000000..e9b4148a6 --- /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: Modbus Typ + 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 000000000..fc14b9938 --- /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: Modbus Typ + 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 000000000..bbae3333d --- /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______ # 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: # 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: + 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: Charger Seriennummer + 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: 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 new file mode 100644 index 000000000..510d76907 --- /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______ # 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: # 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: + 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: Charger Seriennummer + 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: 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 new file mode 100644 index 000000000..1c9dfef81 --- /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______ # 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: # 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: + 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: Charger Seriennummer + 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: 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 new file mode 100644 index 000000000..9f0cc8d18 --- /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______ # 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: # 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: + 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: Charger Seriennummer + 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: 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_0.yaml b/templates/release/de/charger/easee_0.yaml deleted file mode 100644 index 8144e1271..000000000 --- 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 e1ca34184..000000000 --- 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 75a9cb643..000000000 --- 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 6db44a18f..000000000 --- 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 000000000..5096c3107 --- /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: Modbus Typ + 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 000000000..4797ef67d --- /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 000000000..ee0c71692 --- /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 000000000..51f926674 --- /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 000000000..84f82d1c9 --- /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: Modbus Typ + 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 000000000..494ecfff6 --- /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: Modbus Typ + 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 000000000..5e5fbae4b --- /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 7417b1acd..000000000 --- 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 000000000..91dc50e62 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..2ce79aaba --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..f8a643018 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..942e64719 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..f5e8dc999 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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/elli-2_0.yaml b/templates/release/de/charger/elli-2_0.yaml deleted file mode 100644 index 9474c1954..000000000 --- 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 1c5763785..000000000 --- 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 d632dcffd..000000000 --- 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 3c8f2210a..000000000 --- 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 c38f27a64..000000000 --- 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 070b64b6f..000000000 --- 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 c5b447e8f..000000000 --- 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 2e832b39d..000000000 --- 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 f4dc95e58..000000000 --- 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 42d366232..000000000 --- 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 d17fc7023..000000000 --- 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 78ced4df6..000000000 --- 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 000000000..60a699e2a --- /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 000000000..00048ac15 --- /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 000000000..cc93424de --- /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 000000000..753595136 --- /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 000000000..e7c01f0ba --- /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 4595516d7..000000000 --- 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 fa6aa49ba..000000000 --- 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 055b735ac..000000000 --- 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 ee4fa3488..000000000 --- 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 c045860b2..000000000 --- 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 b426e7a0e..000000000 --- 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 95cdf8440..000000000 --- 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 e1ae3bcb1..000000000 --- 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 e130bcc8c..000000000 --- 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 97ea9872e..000000000 --- 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 000000000..9e5e4eba7 --- /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 7edf8d42e..000000000 --- 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 000000000..532cffcb9 --- /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: Modbus Typ + 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 b49c408d6..000000000 --- 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 f3cc2a544..000000000 --- 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 9d40022ab..000000000 --- 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 cc082e51a..000000000 --- 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 000000000..802a3b6ea --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..c780d02c0 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..6d3abd709 --- /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: Modbus Typ + 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 000000000..8e27ebac1 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..956aa3c2c --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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/eprowallbox_0.yaml b/templates/release/de/charger/eprowallbox_0.yaml deleted file mode 100644 index 9f74cf8d5..000000000 --- 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 000000000..dfab43831 --- /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: Modbus Typ + 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 000000000..99625d502 --- /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 f46fb2c3e..000000000 --- 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 000000000..f4dba3451 --- /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 000000000..9dcb739e3 --- /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 408ee7eb4..000000000 --- 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 bba25c0e4..000000000 --- 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 000000000..42cd7deca --- /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 # 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 # 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: # 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 + 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: Zählernummer + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + 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: 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/evbox-livo.yaml b/templates/release/de/charger/evbox-livo.yaml new file mode 100644 index 000000000..3ca4c701f --- /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 000000000..acb1a1ea2 --- /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: Modbus Typ + 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 4f2a93b26..000000000 --- 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 caf6f2072..000000000 --- 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 000000000..4a931562c --- /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 33c11648d..000000000 --- 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 000000000..a7447b64e --- /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: Modbus Typ + 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 000000000..e18da4f2b --- /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: Modbus Typ + 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 000000000..4af801c3d --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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/fritzdect_0.yaml b/templates/release/de/charger/fritzdect_0.yaml deleted file mode 100644 index 247dfd7c6..000000000 --- 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 000000000..52ed47f2d --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..3251c024f --- /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: Modbus Typ + 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 000000000..10a5b62b3 --- /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: Modbus Typ + 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 000000000..e86d44d9a --- /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: Modbus Typ + 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 000000000..0aa1bce99 --- /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: Modbus Typ + 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 c8b4b1b7c..000000000 --- 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 60e62580d..000000000 --- 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 000000000..2bbdf9880 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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-gemini.yaml b/templates/release/de/charger/go-e-charger-gemini.yaml new file mode 100644 index 000000000..00ae8f43c --- /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 000000000..a555f0346 --- /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 000000000..cbed5e9d1 --- /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 000000000..b9e7e3821 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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.yaml b/templates/release/de/charger/go-e-charger-pro.yaml new file mode 100644 index 000000000..836b0d80b --- /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 000000000..abdd58e7a --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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.yaml b/templates/release/de/charger/go-e-charger-v3.yaml new file mode 100644 index 000000000..ecd77842e --- /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 1fb888764..000000000 --- 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 006a89ab5..000000000 --- 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 1bc9b5a2e..000000000 --- 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 9039c6d0a..000000000 --- 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 839e2d187..000000000 --- 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 000000000..6e6b94ced --- /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 000000000..9a9314300 --- /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 000000000..15128f37c --- /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 1ac96480b..000000000 --- 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 f54240d0e..000000000 --- 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 02a8fa4f7..000000000 --- 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 63b821d59..000000000 --- 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 521f72ee0..000000000 --- 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 aca2915fd..000000000 --- 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 000000000..fa52c1456 --- /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: Modbus Typ + 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 2d61df78d..000000000 --- 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 af4454923..000000000 --- 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 29e436825..000000000 --- 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 4e1b9cc73..000000000 --- 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 000000000..3d46beed9 --- /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: Modbus Typ + 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 000000000..e218deeea --- /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: Modbus Typ + 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 f709745da..000000000 --- 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 387c70b2f..000000000 --- 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 000000000..36a9afd95 --- /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 b3ce40b4a..000000000 --- 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 000000000..b37be6f28 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..7596cba27 --- /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, 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, 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, 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) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP-Adresse oder Hostname + help: + advanced: false + optional: false + - name: port + example: BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010 + default: 2010 + choice: [] + unit: + description: XML-RPC-Server Port-Nummer + 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: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2 + default: 6 + choice: [] + unit: + description: Kanalnummer des Power-Meters + help: Kanalnummer des Messwertkanals, wie im CCU Webfrontend angezeigt. + advanced: true + optional: false + - name: switchchannel + example: HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1 + default: 3 + choice: [] + unit: + description: Kanalnummer der schaltbaren Steckdose + 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 + 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 51b6e6ca4..000000000 --- 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 000000000..420e05c8f --- /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 35b369962..000000000 --- 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 000000000..c8d08048a --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..22081a66b --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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/ichargecion_0.yaml b/templates/release/de/charger/ichargecion_0.yaml deleted file mode 100644 index b17e5e89d..000000000 --- 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 2e266ef1b..000000000 --- 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 000000000..44301dbd4 --- /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: Modbus Typ + 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 b2951cb4d..000000000 --- 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 000000000..4366af96e --- /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: Modbus Typ + 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 805ac61c0..000000000 --- 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 628cd3218..000000000 --- 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 a35d5b198..000000000 --- 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 000000000..66c6e7670 --- /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 000000000..1fc49c15d --- /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: Modbus Typ + 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 000000000..0babf196b --- /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: # 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: Token + 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 000000000..f09a4ca55 --- /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: Modbus Typ + 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 000000000..6bf3f522e --- /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: Modbus Typ + 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 000000000..eb8e771f3 --- /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: Modbus Typ + 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 000000000..6944a0797 --- /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: Modbus Typ + 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 000000000..7cc011e1c --- /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: Modbus Typ + 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 000000000..4319e5798 --- /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: Modbus Typ + 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 000000000..b95eb2120 --- /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: Modbus Typ + 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 000000000..1aff489a7 --- /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: Modbus Typ + 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 000000000..812319b57 --- /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: Modbus Typ + 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 000000000..99447e695 --- /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: Modbus Typ + 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 000000000..cfc0d51c6 --- /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: Modbus Typ + 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 99dbde127..000000000 --- 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 73cc12a65..000000000 --- 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 2311c5c22..000000000 --- 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 847f7cf46..000000000 --- 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 f69b93543..000000000 --- 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 8be233b0c..000000000 --- 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 a7fb0fbcb..000000000 --- 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 000000000..e8cf13a61 --- /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 # Watchdog, 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: Watchdog + 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 a4a175260..000000000 --- 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 a0ac73c8a..000000000 --- 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 000000000..2d52154b5 --- /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 000000000..a0d02ec47 --- /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: Modbus Typ + 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 000000000..5286620cf --- /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: Modbus Typ + 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 eb69e1c9f..000000000 --- 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 000000000..753046e24 --- /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: Modbus Typ + 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 000000000..e161e8d2d --- /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: Modbus Typ + 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 000000000..2ee8b9bab --- /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 # Watchdog, 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: Watchdog + 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 bcc843703..000000000 --- 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 186e53c95..000000000 --- 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 c004446d9..000000000 --- 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 000000000..73664d03f --- /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: Modbus Typ + 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 8700ecb0c..000000000 --- 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 88885d6a7..000000000 --- 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 677637919..000000000 --- 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 420f6a0a7..000000000 --- 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 ca9894c54..000000000 --- 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 417b9744c..000000000 --- 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 63ff9bd02..000000000 --- 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 285677baa..000000000 --- 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 3b6d6985b..000000000 --- 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 02666f38a..000000000 --- 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 b193a60ad..000000000 --- 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 000000000..50e5e2215 --- /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: Modbus Typ + 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 000000000..7843df784 --- /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: Modbus Typ + 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 000000000..a10df23ee --- /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: Modbus Typ + 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 000000000..c9d298938 --- /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: Modbus Typ + 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 000000000..e8839e79c --- /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: Modbus Typ + 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 000000000..a35fbca50 --- /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: Modbus Typ + 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 000000000..6adf8faa3 --- /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: Modbus Typ + 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 000000000..8265dbae5 --- /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: Modbus Typ + 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 000000000..c0100ac09 --- /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: Modbus Typ + 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 574993287..000000000 --- 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 b40c85dda..000000000 --- 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 7cd6f0b65..000000000 --- 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 000000000..293e590fa --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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-hcc3_0.yaml b/templates/release/de/charger/mennekes-hcc3_0.yaml deleted file mode 100644 index 327f8b99e..000000000 --- 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 dbcb5fe2d..000000000 --- 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 000000000..9f1bbef54 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..1e1f2435b --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..4e60b584e --- /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: Modbus Typ + 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 000000000..df54388a9 --- /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 # Temperaturquelle, [1, 2, 3] (optional) + scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperaturquelle + 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 000000000..07aeb0f87 --- /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 # Temperaturquelle, [1, 2, 3] (optional) + scale: 1 # Skalierungsfaktor der Leistungsvorgabe, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperaturquelle + 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 000000000..521e8aa13 --- /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 81b0f1102..000000000 --- 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 000000000..d3763756b --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..d043653a6 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 07040fbee..000000000 --- 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 000000000..711542acb --- /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: # MAC Adresse + 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: MAC Adresse + 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 6e06568f0..000000000 --- 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 000000000..370123be3 --- /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 # Phasenumschaltung aktiviert, Erweiterte Funktion "Phasenumschaltung" muss in der NRGkick App aktiviert sein. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: Phasenumschaltung aktiviert + help: 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 000000000..42fb315b1 --- /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: Modbus Typ + 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 bf4300498..000000000 --- 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 b47bf8b17..000000000 --- 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 920581ce8..000000000 --- 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 000000000..1c864d0b8 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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/ocpp-abb-tac_0.yaml b/templates/release/de/charger/ocpp-abb-tac_0.yaml deleted file mode 100644 index d49e471c2..000000000 --- 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 a6ee4bbdf..000000000 --- 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 e8b2388b2..000000000 --- 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 7664a276f..000000000 --- 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 74fc3cda2..000000000 --- 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 3732d9bf0..000000000 --- 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 da537f97e..000000000 --- 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 6849e1f73..000000000 --- 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 b204a5b7d..000000000 --- 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 3ef507746..000000000 --- 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 561d3b505..000000000 --- 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 a23c3ff5f..000000000 --- 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 f027617e9..000000000 --- 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 d11eda37b..000000000 --- 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 86d7ae826..000000000 --- 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 1f9d62264..000000000 --- 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 f6fa835c1..000000000 --- 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 bd2dcfeec..000000000 --- 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 c6bed0d3f..000000000 --- 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 8c4a28ec1..000000000 --- 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 d4ef2bc5f..000000000 --- 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 c730f6b5c..000000000 --- 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 0686c7582..000000000 --- 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 db3aa1e83..000000000 --- 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 160fa8580..000000000 --- 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 f00c789a9..000000000 --- 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 e191e3533..000000000 --- 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 c105d7a4e..000000000 --- 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 70c5852a4..000000000 --- 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 4416b9def..000000000 --- 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 b2e2a620a..000000000 --- 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 5000ce59a..000000000 --- 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 c824f9275..000000000 --- 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 1cdb473cc..000000000 --- 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 0773ee7bd..000000000 --- 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 4ceb3b749..000000000 --- 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 81da526ad..000000000 --- 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 5a8e2ac9e..000000000 --- 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 83e12aca2..000000000 --- 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 000000000..e8f35ec88 --- /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 9920e2ab6..000000000 --- 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 e53819d57..000000000 --- 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 000000000..24abd785f --- /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 cef53f45b..000000000 --- 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 000000000..9ee47fabd --- /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 000000000..eec3b608c --- /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: Modbus Typ + 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 c74044dcc..000000000 --- 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 000000000..26c8912fa --- /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: Modbus Typ + 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 000000000..bd12d6cf9 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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/pantabox_0.yaml b/templates/release/de/charger/pantabox_0.yaml deleted file mode 100644 index eacffea21..000000000 --- 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 000000000..999fca325 --- /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 72e8e0b93..000000000 --- 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 000000000..5a211194a --- /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: Modbus Typ + 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 000000000..33f9e9b86 --- /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: Modbus Typ + 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 000000000..b78a39d60 --- /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: Modbus Typ + 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 aaba4467c..000000000 --- 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 b1a08f4a0..000000000 --- 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 79d496fdd..000000000 --- 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 2b068337e..000000000 --- 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 000d6b204..000000000 --- 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 a753dfbbb..000000000 --- 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 000000000..6b054d7b7 --- /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: Modbus Typ + 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 000000000..11652fe58 --- /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: Modbus Typ + 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 000000000..b17895859 --- /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: Modbus Typ + 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 000000000..4c6627a45 --- /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: Modbus Typ + 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 000000000..1f61e88c0 --- /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: Modbus Typ + 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 000000000..fed35f669 --- /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: Modbus Typ + 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 000000000..d0768126e --- /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: Modbus Typ + 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 761efe9d6..000000000 --- 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 cd186871f..000000000 --- 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 cf6663631..000000000 --- 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 2be0c6926..000000000 --- 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 5aab2de5e..000000000 --- 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 33434ab16..000000000 --- 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 7bdc73f10..000000000 --- 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 6416af0f0..000000000 --- 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 25e23bc1c..000000000 --- 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 47334ad70..000000000 --- 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 63128dfb4..000000000 --- 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 000000000..528efcece --- /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: # Token, API Token + identity: AA123456 # Identity des Ladepunkts + advanced: | + type: template + template: plugchoice + token: # Token, API Token + identity: AA123456 # Identity des Ladepunkts + connector: 1 # Anschluss-ID +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + help: API Token + advanced: false + optional: false + - name: identity + example: AA123456 + default: + choice: [] + unit: + description: Identity des Ladepunkts + help: + advanced: false + optional: false + - name: connector + example: 1 + default: 1 + choice: [] + unit: + description: Anschluss-ID + help: + 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 92fbdf4e2..000000000 --- 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 d11994fda..000000000 --- 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 d6d9ae704..000000000 --- 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 000000000..38029048e --- /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 000000000..26a177db0 --- /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 000000000..9404b73d5 --- /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 8bd09070f..000000000 --- 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 000000000..57c7ad99d --- /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: Modbus Typ + 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 4dfb8cfd2..000000000 --- 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 35708e484..000000000 --- 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 5092cc375..000000000 --- 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 ee9a1bc7e..000000000 --- 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 000000000..6be65142e --- /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: Modbus Typ + 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 000000000..83f2b2b96 --- /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: Modbus Typ + 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 000000000..c194946f4 --- /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: Modbus Typ + 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 000000000..d422a7b8d --- /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: Modbus Typ + 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 3b68b0218..000000000 --- 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 000000000..00495b8b4 --- /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 d26f95886..000000000 --- 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 000000000..129f77be1 --- /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: Modbus Typ + 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 000000000..c0089cc58 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..64e4dcd48 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..a8980129d --- /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: Modbus Typ + 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 080654a25..000000000 --- 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 000000000..a91568a16 --- /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: Modbus Typ + 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 000000000..35eb05e99 --- /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: Modbus Typ + 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 000000000..1c72fd10a --- /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: Modbus Typ + 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 000000000..d107064df --- /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 # Kanal, 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 # 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) + 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: Kanal + 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 000000000..f5a32ce9f --- /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 # Kanal, 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 # 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) + 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: Kanal + 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 000000000..d0ea70bd5 --- /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 # Kanal, 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 # 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) + 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: Kanal + 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 000000000..c15a6d97c --- /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 # Kanal, 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 # 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) + 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: Kanal + 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 cd0b8d0f0..000000000 --- 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 000000000..77a2b7a8e --- /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: Modbus Typ + 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 000000000..899b112fe --- /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 000000000..733a4a5fc --- /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 000000000..685aa667e --- /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 000000000..e41f5f120 --- /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 000000000..b474be89c --- /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 000000000..8cb9bde40 --- /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 000000000..d9a6f2c1c --- /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 89f47e8f1..000000000 --- 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 7bc3b1823..000000000 --- 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 4ef89c2ed..000000000 --- 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 000000000..152577676 --- /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: Modbus Typ + 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 000000000..f34a51d83 --- /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 f98b8afc1..000000000 --- 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 000000000..829311ada --- /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: Modbus Typ + 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 000000000..6a57622ff --- /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: Modbus Typ + 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 05065ed30..000000000 --- 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 d608c0925..000000000 --- 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 24f484d8e..000000000 --- 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 000000000..5920ce43d --- /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 000000000..5cd5ab6c3 --- /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: Modbus Typ + 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 000000000..263217957 --- /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: Modbus Typ + 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 000000000..58fcfe55a --- /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: Modbus Typ + 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 000000000..becde93e2 --- /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: Modbus Typ + 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 5b8f2235c..000000000 --- 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 30859d9c1..000000000 --- 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 2ffc3d6fb..000000000 --- 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 000000000..748742b15 --- /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: Modbus Typ + 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 000000000..32289fa1b --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..fd1c80658 --- /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: Modbus Typ + 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 84322afc6..000000000 --- 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 13687bf67..000000000 --- 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 691ea518a..000000000 --- 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 000000000..34eec6a8e --- /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 2d99cb82c..000000000 --- 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 000000000..4421304e5 --- /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: Modbus Typ + 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 000000000..35102e8fe --- /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: Modbus Typ + 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 000000000..7ec06ed58 --- /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 000000000..ef5dd9437 --- /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 # 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... + 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: 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/tessie_0.yaml b/templates/release/de/charger/tessie_0.yaml deleted file mode 100644 index 763f872d5..000000000 --- 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 000000000..d11732093 --- /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: Modbus Typ + 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 000000000..c6b95305d --- /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: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (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: # 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: + - 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: Energiemanager MQTT Topic + help: WEM Firmware v2 erforderlich. + 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 000000000..793324af5 --- /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: # Energiemanager MQTT Topic, WEM Firmware v2 erforderlich. (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: # 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: + - 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: Energiemanager MQTT Topic + help: WEM Firmware v2 erforderlich. + 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 000000000..4dae9f1ca --- /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 000000000..190a59edf --- /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 777edb0dd..000000000 --- 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 d89068290..000000000 --- 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 99329162a..000000000 --- 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 dc6fcf72d..000000000 --- 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 000000000..e02bc6028 --- /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 000000000..a70bc3ff4 --- /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 862457b9e..000000000 --- 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 2bda8f5e1..000000000 --- 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 79f79c6e5..000000000 --- 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 000000000..683cd8142 --- /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: Modbus Typ + 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 000000000..08cd5c6cc --- /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 000000000..db14fb3f7 --- /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 # Region, [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: Region + help: + advanced: false + optional: true + - name: zone + example: + default: + choice: [] + unit: + description: ID der Boostzone + help: + advanced: false + optional: true + - name: setpoint + example: + default: + choice: [] + unit: + description: Boost Temperatur + help: + 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 5192cd587..000000000 --- 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 6f095ac40..000000000 --- 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 000000000..ba6cd4ffa --- /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: Modbus Typ + 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 000000000..eeb2c7c2b --- /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: Modbus Typ + 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 c3da79ac2..000000000 --- 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 84470c63e..000000000 --- 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 c677bc61d..000000000 --- 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 8f23c8bda..000000000 --- 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 e3c651bcc..000000000 --- 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 000000000..8c7e8b03b --- /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: Modbus Typ + 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 000000000..4147fd8cd --- /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: Modbus Typ + 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 410967397..000000000 --- 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 7e0a575de..000000000 --- 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 000000000..b60f612e3 --- /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 5f39bb4b1..000000000 --- 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 000000000..341632bcd --- /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: Modbus Typ + 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 000000000..24e3e0dbf --- /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 000000000..5c1d27519 --- /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 000000000..b73783072 --- /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 000000000..7c37ec6de --- /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 000000000..2df57dd47 --- /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 000000000..2a57f8dbb --- /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: # 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: Token + 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: 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 new file mode 100644 index 000000000..59dac72a1 --- /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: # 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: Token + 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: 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 new file mode 100644 index 000000000..3cafbd32f --- /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: # 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: Token + 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: 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 new file mode 100644 index 000000000..30d84a4dd --- /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: # 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: Token + 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: Seriennummer + 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 8e66d0276..000000000 --- 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 80c8e993e..000000000 --- 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 d4ec84c01..000000000 --- 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 2931d640b..000000000 --- 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 000000000..0d866fa2a --- /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: Modbus Typ + 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 000000000..f71df5a49 --- /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: Modbus Typ + 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 000000000..69e29d4ec --- /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: Modbus Typ + 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 000000000..31cf20c32 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..23fc4b944 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..2cfeea6dc --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..cb7f1dec3 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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-fw5_0.yaml b/templates/release/de/charger/wallbox-fw5_0.yaml deleted file mode 100644 index 70d000776..000000000 --- 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 bbf605765..000000000 --- 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 592572571..000000000 --- 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 cf2b6ef89..000000000 --- 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 000000000..0b8c545da --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..fb192e8bb --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..6b76d1eca --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..bdee3df40 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..3aaefbc2a --- /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: Modbus Typ + 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 000000000..c5215f41f --- /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: Modbus Typ + 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 000000000..cd6446d5a --- /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 150b0916d..000000000 --- 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 4b1d540c7..000000000 --- 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 000000000..b3cc480e8 --- /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: Modbus Typ + 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 000000000..ede3bf112 --- /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 b8cf338a7..000000000 --- "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 000000000..323786a89 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..cb09101a1 --- /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 (K), 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 (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: Modbus Typ + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Anhebung der Heizwassertemperatur + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Anhebung der Warmwassertemperatur + help: 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 000000000..ac9e70588 --- /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: # 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: ID + 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 000000000..b0a6ffb9b --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..12d1ce84c --- /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: # 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: ID + 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 000000000..54d0b582c --- /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: # 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: ID + 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 d6f026688..000000000 --- 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 ca11a7a24..000000000 --- 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 3f05593ea..000000000 --- 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 000000000..a8b0398dc --- /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 # Watchdog, 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: 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 new file mode 100644 index 000000000..19ee78278 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Zeitlimit für die Registrierung + help: Zeitlimit für die Registrierung des Ladepunktes + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Übertragungsintervall der Zählerwerte + help: Zeitintervall für die Übertragung der Zählerwerte (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..696678de3 --- /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 # Verzögerung, 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 # Verzögerung, 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 # Verzögerung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Typ + 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: Verzögerung + 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 000000000..3228fb4bc --- /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: Modbus Typ + 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 000000000..1b4917bf0 --- /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: Modbus Typ + 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 8555cd10c..000000000 --- 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 000000000..a62d281f3 --- /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: Modbus Typ + 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 000000000..9bcd42b72 --- /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: Modbus Typ + 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 8c3bc2e02..000000000 --- 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 219c7e420..000000000 --- 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 000000000..c68655690 --- /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: Modbus Typ + 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 158d7b005..000000000 --- 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 000000000..31644be2c --- /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: Modbus Typ + 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 c6fbcfa47..000000000 --- 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 000000000..b0b01245f --- /dev/null +++ b/templates/release/de/meter/alpha-ess-storion-smile.yaml @@ -0,0 +1,211 @@ +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 + - 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 + 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: Modbus Typ + 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 000000000..f6bcb3572 --- /dev/null +++ b/templates/release/de/meter/ampere-ampere-storagepro.yaml @@ -0,0 +1,207 @@ +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 + - 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 + - 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: Modbus Typ + 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 000000000..040b18f60 --- /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: Modbus Typ + 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 000000000..790a3a8e9 --- /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 74bd19b9a..000000000 --- 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 000000000..7e38573c6 --- /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 000000000..4d053f883 --- /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: Modbus Typ + 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 000000000..0aeae72e6 --- /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: Modbus Typ + 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 14bc06d87..000000000 --- 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 13119038a..000000000 --- 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 000000000..660b55714 --- /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: Modbus Typ + 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 000000000..ccbbfd0a8 --- /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: Modbus Typ + 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 000000000..ef0ce9c2d --- /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 24872b878..000000000 --- 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 000000000..a95b46a13 --- /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: Modbus Typ + 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 000000000..21ca50a01 --- /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: Modbus Typ + 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 000000000..b814dbe08 --- /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: Modbus Typ + 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 000000000..483096302 --- /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: Modbus Typ + 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 000000000..8977fd01e --- /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: Modbus Typ + 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 000000000..f2415e6b2 --- /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: Modbus Typ + 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 000000000..d11eafa3f --- /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: Modbus Typ + 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 000000000..8316fa805 --- /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: Modbus Typ + 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 000000000..be3897581 --- /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: Modbus Typ + 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 c7b87e0fc..000000000 --- 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 75aa358e1..000000000 --- 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 c67f2a32e..000000000 --- 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 569c31be3..000000000 --- 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 eb7ce78fb..000000000 --- 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 f888b1d08..000000000 --- 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 2e307a267..000000000 --- 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 c9e82d203..000000000 --- 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 20f08771e..000000000 --- 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 5d4dad42c..000000000 --- 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 c2d1600b6..000000000 --- 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 7235030cd..000000000 --- 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 335ed59fe..000000000 --- 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 000000000..ec68afe17 --- /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 65d994187..000000000 --- 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 000000000..df761caf5 --- /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 7850c682e..000000000 --- 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 000000000..20d45d592 --- /dev/null +++ b/templates/release/de/meter/deye-3p-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Typ + 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 000000000..1b4f7aa07 --- /dev/null +++ b/templates/release/de/meter/deye-hp3-hybrid-inverter.yaml @@ -0,0 +1,232 @@ +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 # Nummer des Batteriespeichers, 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 # Nummer des Batteriespeichers, 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 # 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) + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Nummer des Batteriespeichers + 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 5c3bc6d3c..000000000 --- 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 dc40f5fac..000000000 --- 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 829be8f3b..000000000 --- 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 31f546e2d..000000000 --- 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 330b3dd9a..000000000 --- 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 aef8b4506..000000000 --- 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 02fbe72af..000000000 --- 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 8a119828b..000000000 --- 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 000000000..136c4b000 --- /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: Modbus Typ + 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 000000000..e03ce9644 --- /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: Modbus Typ + 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 e25819981..000000000 --- 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 8abcf56b7..000000000 --- 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 000000000..2147fcd20 --- /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: Modbus Typ + 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 b584ebb31..000000000 --- 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 b1959c296..000000000 --- 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 000000000..df382b542 --- /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 # Zählernummer + - 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 # Zählernummer +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: Zählernummer + 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 b32631de5..000000000 --- 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 000000000..c20c3a811 --- /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 2586b6d37..000000000 --- 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 000000000..4eabb1f46 --- /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: Modbus Typ + 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 944659a79..000000000 --- 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 000000000..6cc7a3344 --- /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: # RSCP-Password + 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: # RSCP-Password + 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: # RSCP-Password + 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: # 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 + 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: # RSCP-Password + 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: # RSCP-Password + 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: RSCP-Password + 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 5c940f94e..000000000 --- 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 000000000..3760971d3 --- /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: Modbus Typ + 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 c523f2787..000000000 --- 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 000000000..c4356964b --- /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: Modbus Typ + 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 52e4d9b14..000000000 --- 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 17900c48e..000000000 --- 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 dc9eab47b..000000000 --- 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 000000000..039de5eaa --- /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: Modbus Typ + 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 bbc7de94e..000000000 --- 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 000000000..956eced6c --- /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: Modbus Typ + 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 000000000..e3b1948ee --- /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: Modbus Typ + 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 c15d696c0..000000000 --- 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 dbc823ff7..000000000 --- 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 02e511569..000000000 --- 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 3086ab92f..000000000 --- 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 407eedce6..000000000 --- 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 000000000..a6de08539 --- /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: # 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: # 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: # 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: # 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: # 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: # 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: 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 + - 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 9d85fe128..000000000 --- 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 e4071421d..000000000 --- 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 000000000..d0abc794b --- /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 000000000..527965ccd --- /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 000000000..8f3ea97ca --- /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 # Watchdog, 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: Steuerbare Batterie Komponente + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: Watchdog + 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 5e59afc06..000000000 --- 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 f4845b0e9..000000000 --- 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 97c77b3ab..000000000 --- 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 000000000..954940318 --- /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: Modbus Typ + 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 000000000..f0b86c216 --- /dev/null +++ b/templates/release/de/meter/foxess-h3-series-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Typ + 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 000000000..337a63b59 --- /dev/null +++ b/templates/release/de/meter/foxess-h3-smart-series-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Typ + 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 b25f7e9f3..000000000 --- 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 bddc2cc7d..000000000 --- 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 01aacb0db..000000000 --- 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 000000000..7c77e4bb1 --- /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 4899aae13..000000000 --- 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 000000000..8e07e0f5a --- /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 # 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 + 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: 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 + - 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 000000000..cfe9b7c77 --- /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: Modbus Typ + 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 000000000..ec286a57f --- /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 # Batteriekonfigurations-URI, 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 # Batteriekonfigurations-URI, 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 # Batteriekonfigurations-URI, 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: 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-solarapi-v1_0.yaml b/templates/release/de/meter/fronius-solarapi-v1_0.yaml deleted file mode 100644 index a1b28239e..000000000 --- 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 000000000..62bfcbb66 --- /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 # 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 + 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: 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 + - 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 000000000..38a0a0eda --- /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: Modbus Typ + 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 000000000..4623fd8f6 --- /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: Modbus Typ + 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 000000000..53e7a2c36 --- /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: Modbus Typ + 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 000000000..88aa70d39 --- /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 28b9140a6..000000000 --- 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 f4a2cd4b5..000000000 --- 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 000000000..68006b22f --- /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 # Batteriespeichernummer, [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 # Batteriespeichernummer, [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 # Batteriespeichernummer, [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 # Batteriespeichernummer, [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 # Batteriespeichernummer, [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 # Batteriespeichernummer, [1, 2] (optional) + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip', 'udp'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: battery + example: + default: 1 + choice: ['1', '2'] + unit: + description: Batteriespeichernummer + 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 000000000..d6a2350af --- /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 d0ad29018..000000000 --- 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 000000000..0231d53ac --- /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: Modbus Typ + 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 302986981..000000000 --- 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 000000000..1f05cd622 --- /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: Modbus Typ + 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 15bd36a6f..000000000 --- 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 81e601ddb..000000000 --- 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 000000000..8b4c44680 --- /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: Modbus Typ + 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 000000000..034430b26 --- /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, 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, 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 + 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, 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, 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 + 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, 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, 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 + 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: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1 + default: 6 + choice: [] + unit: + 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 + - name: cache + example: 5m + default: 1s + choice: [] + unit: + 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/homematic_0.yaml b/templates/release/de/meter/homematic_0.yaml deleted file mode 100644 index 703dd245d..000000000 --- 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 000000000..1747f8c5c --- /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 8e3458650..000000000 --- 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 000000000..2c7ff6ad0 --- /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 4ccb23f89..000000000 --- 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 44b5f853b..000000000 --- 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 000000000..2e1fdce17 --- /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 + 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/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 000000000..d3872c682 --- /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 3017a6306..000000000 --- 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 ff624097e..000000000 --- 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 000000000..a9ff0156d --- /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: Modbus Typ + 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 5cec29505..000000000 --- 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 000000000..0e8b9398f --- /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 # Nummer des Batteriespeichers, 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 # Nummer des Batteriespeichers, 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 # Nummer des Batteriespeichers, optional + capacity: 50 # Akkukapazität (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Nummer des Batteriespeichers + 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 d476b93ea..000000000 --- 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 000000000..c76459f6b --- /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: Modbus Typ + 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 000000000..c026ff295 --- /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 # Nummer des Batteriespeichers, 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 # Nummer des Batteriespeichers, 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 # 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) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Typ + 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: Nummer des Batteriespeichers + 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 03b2b4463..000000000 --- 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 000000000..5c568947d --- /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 000000000..a04c2db33 --- /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 c2963ace2..000000000 --- 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 2db41ae12..000000000 --- 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 000000000..a0a006e1c --- /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 000000000..384351158 --- /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: Modbus Typ + 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 a72a94dd1..000000000 --- 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 000000000..4096e5849 --- /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 9dba55086..000000000 --- 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 000000000..88b60f485 --- /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: Modbus Typ + 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 000000000..7843426eb --- /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: Modbus Typ + 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 1c8d9b69f..000000000 --- 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 000000000..5549ab7dd --- /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: Modbus Typ + 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 8ac865893..000000000 --- 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 000000000..fb93a948d --- /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: Modbus Typ + 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 000000000..fbe79d304 --- /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: Modbus Typ + 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 2481f1a06..000000000 --- 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 a2d146cf9..000000000 --- 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 000000000..156f5062d --- /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 000000000..eceeb338f --- /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 d8f1aba73..000000000 --- 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 000000000..daa9f3586 --- /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 065340d99..000000000 --- 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 000000000..f6509783c --- /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 5162ec873..000000000 --- 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 304a091b2..000000000 --- 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 f0caf8f8b..000000000 --- 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 000000000..bf74ed89b --- /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 18b9a1eb9..000000000 --- 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 000000000..f4d4fa8f7 --- /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 # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Watchdog + 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 000000000..6384072b2 --- /dev/null +++ b/templates/release/de/meter/kostal-plenticore-hybrid.yaml @@ -0,0 +1,131 @@ +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 + watchdog: 60s # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Watchdog + 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 35eaa37f0..000000000 --- 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 000000000..eff0b09aa --- /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: Modbus Typ + 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 000000000..1764a257c --- /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: Modbus Typ + 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 000000000..0bc73961d --- /dev/null +++ b/templates/release/de/meter/lg-ess-home-15.yaml @@ -0,0 +1,107 @@ +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, Nummer des LG ESS HOME Wechselrichters. (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, Nummer des LG ESS HOME Wechselrichters. (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, 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) +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: Registriernummer + help: Nummer 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 a3f0893d3..000000000 --- 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 000000000..850c22d28 --- /dev/null +++ b/templates/release/de/meter/lg-ess-home-8-10.yaml @@ -0,0 +1,110 @@ +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, Nummer des LG ESS HOME Wechselrichters. (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, Nummer des LG ESS HOME Wechselrichters. (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, 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) +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: Registriernummer + help: Nummer 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 56efaf74a..000000000 --- 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 000000000..22b2ac5fa --- /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 7e5c8130c..000000000 --- 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 000000000..0e9f5ecf5 --- /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: Modbus Typ + 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 000000000..972a91871 --- /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: Modbus Typ + 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 000000000..dd87bddb3 --- /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 # 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 # 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: Modbus Typ + 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: 11 + default: 11 + choice: [] + unit: '%' + description: Minimaler Ladestand + help: Venus kann nur bis 11% entladen werden. + 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: Maximale Ladeleistung + help: 2500W ist das Maximum für Venus. + advanced: true + optional: true + - name: work_mode_normal + example: + default: 1 + choice: [] + unit: + description: Work mode für Normal-Modus + help: 0=manuell, 1=Eigenverbrauch, 2=AI-Optimierung. + 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 cc5205b39..000000000 --- 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 000000000..bce07c0e1 --- /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 e3d65077f..000000000 --- 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 de33af612..000000000 --- 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 b04708924..000000000 --- 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 000000000..5086d2373 --- /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 000000000..d980ca6a3 --- /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 000000000..2e37b072a --- /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 000000000..a03ea2b1f --- /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: Modbus Typ + 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 f8d60b48a..000000000 --- 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 000000000..4184598ae --- /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 4be2b4a63..000000000 --- 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 000000000..f22126abc --- /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 # Watchdog, 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: Steuerbare Batterie Komponente + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: Watchdog + 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 63c4787d4..000000000 --- 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 f37725bdd..000000000 --- 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 000000000..7683a5384 --- /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: Modbus Typ + 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 000000000..a47ee96e0 --- /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: Modbus Typ + 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 775ad5c2d..000000000 --- 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 000000000..4239758db --- /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 75df84cd0..000000000 --- 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 000000000..f68f2309c --- /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: Modbus Typ + 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 99d762b14..000000000 --- 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 000000000..13dc3e736 --- /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: Modbus Typ + 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 e8ffec3dd..000000000 --- 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 000000000..880199f48 --- /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, 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, 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: ID + 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 9b6536050..000000000 --- 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 e3788f5c3..000000000 --- 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 000000000..8d0d1fecd --- /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 000000000..f065eb4bc --- /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 # Dritter PV-Eingang, 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 # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, 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 # Dritter PV-Eingang, 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 # 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: | + 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 # Dritter PV-Eingang, 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 # 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: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: Dritter PV-Eingang + help: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Nummer des Batteriespeichers + 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 000000000..a85acde75 --- /dev/null +++ b/templates/release/de/meter/rct-power.yaml @@ -0,0 +1,112 @@ +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 + cache: 30s # Cache, Zeitintervall nach dem Daten erneut vom Fahrzeug abgefragt werden (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 + 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) +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 d485fdb98..000000000 --- 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 000000000..329f985de --- /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: Modbus Typ + 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 000000000..ebba403e8 --- /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: Modbus Typ + 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 000000000..229faa061 --- /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: Modbus Typ + 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 db5c0070c..000000000 --- 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 000000000..da618747c --- /dev/null +++ b/templates/release/de/meter/saj-h2-series-hybrid-solar-inverter.yaml @@ -0,0 +1,207 @@ +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 + - 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 + - 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: Modbus Typ + 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 048623b02..000000000 --- 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 cc4c69e04..000000000 --- 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 000000000..fd78d22c6 --- /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: Modbus Typ + 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 dcf6d62b7..000000000 --- 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 000000000..01f7d29c7 --- /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: Modbus Typ + 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 6b87e7b5f..000000000 --- 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 0932eb8d3..000000000 --- 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 000000000..14be7ebc9 --- /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: Modbus Typ + 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 c766da31f..000000000 --- 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 000000000..165368013 --- /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 # Schema, [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + 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 # Schema, [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + 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 # Schema, [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + schema: https # Schema, [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: Schema + 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 f3ef29593..000000000 --- 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 000000000..824bc8cf4 --- /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: Modbus Typ + 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 9a544572a..000000000 --- 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 1d9c00fb4..000000000 --- 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 000000000..bbd8ea9b0 --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: 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 new file mode 100644 index 000000000..e7a37b78a --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: Kanal + 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 3a058acc6..000000000 --- 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 000000000..7e8ebab9d --- /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 aadea8b57..000000000 --- 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 000000000..935e03a4f --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: 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 new file mode 100644 index 000000000..ac36b43a4 --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: 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 new file mode 100644 index 000000000..e3e29f3ba --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: 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 new file mode 100644 index 000000000..867e84f61 --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: Kanal + 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 000000000..eb4100b02 --- /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 000000000..07ca0d2ec --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: Kanal + 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 5287e9eb9..000000000 --- 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 000000000..1e872f545 --- /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 # Kanal, 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 # Kanal, 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 # Kanal, 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: 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 new file mode 100644 index 000000000..6da9b0bee --- /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: Modbus Typ + 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 938c0727f..000000000 --- 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 000000000..3b7af8f1f --- /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: Modbus Typ + 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 e9bc6c314..000000000 --- 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 000000000..2f6bb7a92 --- /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: Modbus Typ + 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 f4a8b1239..000000000 --- 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 000000000..cfe9bf741 --- /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 # ID, optional + advanced: | + type: template + template: sigenergy + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # ID, 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 # ID, optional + advanced: | + type: template + template: sigenergy + usage: pv + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # ID, 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 # ID, optional + advanced: | + type: template + template: sigenergy + usage: battery + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 502 # Port, optional + id: 1 # ID, 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: ID + 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 6a5b26041..000000000 --- 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 bbcd50edf..000000000 --- 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 bfb89cd89..000000000 --- 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 8a5605e84..000000000 --- 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 e6c484c15..000000000 --- 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 5abf7efa2..000000000 --- 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 000000000..4c11da87e --- /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: Modbus Typ + 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 7c38f5c96..000000000 --- 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 000000000..b9fddbb8c --- /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 a95d06d01..000000000 --- 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 39ba851d7..000000000 --- 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 c4a322170..000000000 --- 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 cda83af75..000000000 --- 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 000000000..da436c855 --- /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 86c07ccbd..000000000 --- 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 e8d1288ce..000000000 --- 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 d992bdfcf..000000000 --- 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 390952c08..000000000 --- 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 000000000..d9ee39797 --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Watchdog + 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 000000000..209cebbb0 --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Watchdog + 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 000000000..ca7de8047 --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Watchdog + 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 000000000..191be61b5 --- /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 000000000..be7bc123e --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Watchdog + 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 000000000..42781b632 --- /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: Modbus Typ + 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 2d6962964..000000000 --- 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 000000000..53b65db08 --- /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: Modbus Typ + 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 000000000..e8f8f078d --- /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 c2cb69514..000000000 --- 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 000000000..9c2a0507e --- /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 000000000..ed13eaa4a --- /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 000000000..9b12cf1c7 --- /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 000000000..f35af7cc1 --- /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 000000000..12fbfb7db --- /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 000000000..4c9e878fd --- /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 000000000..7bdb46e55 --- /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 6e0a3bf22..000000000 --- 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 d57c84827..000000000 --- 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 be2fe291a..000000000 --- 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 41d874601..000000000 --- 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 ac178d41d..000000000 --- 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 000000000..adbe1260e --- /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: Modbus Typ + 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 000000000..655dde19f --- /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: Modbus Typ + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 000000000..d401bdef7 --- /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: Modbus Typ + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 000000000..8e5042656 --- /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: Modbus Typ + 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 000000000..4dd2d5834 --- /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: Modbus Typ + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 000000000..cf449b68a --- /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: Modbus Typ + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 aabea2282..000000000 --- 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 73e04dfc7..000000000 --- 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 000000000..a8f3899d7 --- /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 48718aad3..000000000 --- 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 000000000..f57f08359 --- /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 # Watchdog, 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 # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: Modbus Typ + 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: Watchdog + 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 9ed728808..000000000 --- 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 000000000..11db5eca1 --- /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: Modbus Typ + 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 a96acbb31..000000000 --- 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 000000000..539b0b434 --- /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 0c6b7145f..000000000 --- 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 17dd0ec4c..000000000 --- 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 000000000..14206ad0e --- /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 # Watchdog, 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 # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Typ + 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: Watchdog + 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 26cd9e902..000000000 --- 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 177b29e4e..000000000 --- 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 000000000..5c872413f --- /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: Modbus Typ + 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 000000000..0d41a2fa4 --- /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: Modbus Typ + 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 000000000..41f71e88c --- /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 000000000..aa02b3831 --- /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 d78b9d9f2..000000000 --- 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 000000000..ba7163d1f --- /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 000000000..6a62c11ff --- /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 9618db1a4..000000000 --- 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 000000000..59f6ffdb0 --- /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 e00a42656..000000000 --- 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 ef9d59c6d..000000000 --- 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 b84f6d46e..000000000 --- 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 000000000..536cd48e4 --- /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 000000000..c4679b271 --- /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 # Dritter PV-Eingang, 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 # Dritter PV-Eingang, Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) (optional) + storageunit: 1 # Nummer des Batteriespeichers, 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 # Dritter PV-Eingang, 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 # 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: | + 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 # Dritter PV-Eingang, 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 # 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: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: Dritter PV-Eingang + help: Der Wechselrichter hat einen dritten PV-Eingang (MPPT3) + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Nummer des Batteriespeichers + 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 000000000..01b891f2a --- /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 4b92cb14b..000000000 --- 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 8c86884e4..000000000 --- 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 3298fca71..000000000 --- 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 000000000..4a656b775 --- /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 # Verzögerung, 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 # Verzögerung, 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 # Verzögerung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Typ + 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: Verzögerung + 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 ee694fa3c..000000000 --- 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 82b4dacf8..000000000 --- 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 471ad04ed..000000000 --- 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 060c4546d..000000000 --- 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 000000000..86e0e3ac1 --- /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 000000000..f1cdab990 --- /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 000000000..5d1da0d9d --- /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 000000000..fa3c8646a --- /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 000000000..7a6600d6e --- /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: # 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: # 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: Token + 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 7f7e19f87..000000000 --- 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 5b0735b29..000000000 --- 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 000000000..f4f90bf5f --- /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 # Verzögerung, 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 # Verzögerung, 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 # Verzögerung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Typ + 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: Verzögerung + 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 000000000..a63ed7e1a --- /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 6a93bdd4f..000000000 --- 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 c8e5ddc05..000000000 --- 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 3bc755a5b..000000000 --- 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 000000000..b964c24ab --- /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: Modbus Typ + 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 000000000..0d287b446 --- /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: Modbus Typ + 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 893b81ef3..000000000 --- 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 000000000..f31c280b6 --- /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: Modbus Typ + 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 000000000..56ec4b0eb --- /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: Modbus Typ + 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 000000000..78c482bb9 --- /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: Modbus Typ + 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 56fc6b6d0..000000000 --- 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 0cac73304..000000000 --- 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 000000000..f46a7bd8a --- /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: Modbus Typ + 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 821d3f3d1..000000000 --- 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 000000000..8e9782d48 --- /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: Modbus Typ + 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 4e1856e3c..000000000 --- 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 fad003856..000000000 --- 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 000000000..4ddc17575 --- /dev/null +++ b/templates/release/de/meter/sunsynk-3p-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Typ + 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 000000000..7cf237da6 --- /dev/null +++ b/templates/release/de/meter/sunsynk-hp3-hybrid-inverter.yaml @@ -0,0 +1,232 @@ +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 # Nummer des Batteriespeichers, 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 # Nummer des Batteriespeichers, 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 # 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) + includegenport: # GEN-Anschluss als Solar-Eingang verwenden, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Typ + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Nummer des Batteriespeichers + 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 000000000..029a23837 --- /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: Modbus Typ + 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 000000000..6df9f4f04 --- /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: Modbus Typ + 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 000000000..5ecd78150 --- /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: Modbus Typ + 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 000000000..1ebea79f7 --- /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 # Verzögerung, 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 # Verzögerung, 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 # Verzögerung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Typ + 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: Verzögerung + 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 41d94d899..000000000 --- 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 319c76ecc..000000000 --- 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 000000000..8e270d647 --- /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 bb5ae3345..000000000 --- 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 000000000..002558a06 --- /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 000000000..07916271e --- /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 3744be789..000000000 --- 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 000000000..6fbd8bce9 --- /dev/null +++ b/templates/release/de/meter/tesla-powerwall.yaml @@ -0,0 +1,123 @@ +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: # 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: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (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: # 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: # Refresh token, optional + siteId: # Site ID, optionale Product ID dieser Energy Site, zum Übersteuern der automatischen Erkennung (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: # 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: # 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: + - 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: Refresh token + help: + advanced: false + optional: true + - name: siteId + example: + default: + choice: [] + unit: + description: Site ID + 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 0cbb9a7b1..000000000 --- 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 0c93f82c0..000000000 --- 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 000000000..ef324fdd3 --- /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 # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional +params: + - name: token + example: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE + default: + choice: [] + unit: + description: Token + help: + advanced: false + optional: false + - name: homeid + example: 96a14971-525a-4420-aae9-e5aedaa129ff + default: + choice: [] + unit: + description: Home ID + 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 6da33b3f3..000000000 --- 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 000000000..5a8e95978 --- /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 000000000..a84c861e4 --- /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 e7b9fde4e..000000000 --- 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 b6d0652b6..000000000 --- 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 8f9d89f92..000000000 --- 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 000000000..321ca257f --- /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 000000000..248775869 --- /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 000000000..db5ff58ee --- /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 000000000..2cfdefb49 --- /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 000000000..f3af3a710 --- /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 1a260fd1b..000000000 --- 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 000000000..2971591ab --- /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: Modbus Typ + 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 000000000..2539a16e1 --- /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: Modbus Typ + 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 000000000..89b53122e --- /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: Modbus Typ + 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 000000000..7e854c89b --- /dev/null +++ b/templates/release/de/meter/victron-energy.yaml @@ -0,0 +1,118 @@ +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 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 Instanz, Kann im VRM Portal oder im RemoteUI ausgelesen werden. (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 + - 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: Grid-Energiezähler VRM Instanz + help: 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 ab70a35b9..000000000 --- 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 000000000..2dbd183e3 --- /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: Modbus Typ + 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 52564aa2d..000000000 --- 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 aa893ebde..000000000 --- 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 b5d795d4a..000000000 --- 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 000000000..3eee2a172 --- /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: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID +params: + - name: url + example: http://zaehler.network.local:8080/api/data + default: + choice: [] + unit: + description: Middleware URL + help: + advanced: false + optional: true + - name: importuuid + example: + default: + choice: [] + unit: + description: Import UUID + help: + advanced: false + optional: false + - name: exportuuid + example: + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..db4829470 --- /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: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID +params: + - name: url + example: http://zaehler.network.local:8080/api/data + default: + choice: [] + unit: + description: Middleware URL + help: + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..e9da5931d --- /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: # 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: 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 new file mode 100644 index 000000000..9ad776303 --- /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: # UUID + advanced: | + type: template + template: vzlogger + usage: grid + host: 192.0.2.2 # IP-Adresse oder Hostname + port: 8081 # Port, optional + uuid: # UUID + scale: 1 # Skalierungsfaktor, Multipliziere Rohwert mit diesem Faktor (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 + 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: UUID + 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: 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + 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 9e31137f7..000000000 --- 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 000000000..1119969ce --- /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: Modbus Typ + 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 4b3f34dd3..000000000 --- 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 000000000..3db4e6666 --- /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 # Verzögerung, 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 # Verzögerung, 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 # Verzögerung, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Typ + 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: Verzögerung + 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 bedbb1204..000000000 --- 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 8327b9417..000000000 --- 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 418d78c2f..000000000 --- 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 da31402d4..000000000 --- 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 779a7375a..000000000 --- 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 000000000..9ac0b5ea9 --- /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: Modbus Typ + 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 000000000..a360a8fab --- /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: Modbus Typ + 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 000000000..4f239fd56 --- /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: Modbus Typ + 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 000000000..5ec5b3cb5 --- /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: Modbus Typ + 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 000000000..46ea11325 --- /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 7753a7cd1..000000000 --- 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 000000000..6948af583 --- /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: Modbus Typ + 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 000000000..8e5f535b1 --- /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: Modbus Typ + 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 000000000..79729c259 --- /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 # 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 # 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 # 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 # 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: + - name: account + example: dev@zendure.com + default: + choice: [] + unit: + description: Account ID + help: + advanced: false + optional: false + - name: serial + example: VU5D99F74021B04 + default: + choice: [] + unit: + description: Seriennummer + 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: Region + 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 7369b2ed7..000000000 --- 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 000000000..9f36a7b43 --- /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 000000000..b199b9b31 --- /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 000000000..c6627cce3 --- /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 000000000..fd644ed4d --- /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: # Token, optional + siteid: # Site ID, optional + channel: # Kanal, optional + advanced: | + type: template + template: amber + 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) +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + help: + advanced: false + optional: true + - name: siteid + example: + default: + choice: [] + unit: + description: Site ID + help: + advanced: false + optional: true + - name: channel + example: + default: + choice: [] + unit: + description: Kanal + 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 426aefc2f..000000000 --- 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 000000000..f777a8d05 --- /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 # Region, [DE, AT] + advanced: | + type: template + template: awattar + 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) +params: + - name: region + example: AT + default: + choice: ['DE', 'AT'] + unit: + description: Region + 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 18a940678..000000000 --- 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 000000000..d6611e761 --- /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: # Token + zone: DE # Zone, 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: Token + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..5e0534254 --- /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: # Token + zone: DE # Zone, siehe https://api.electricitymap.org/v3/zones +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + 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/electricitymaps-free_0.yaml b/templates/release/de/tariff/electricitymaps-free_0.yaml deleted file mode 100644 index 141fdeec0..000000000 --- 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 c483166fe..000000000 --- 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 000000000..b54f7cbea --- /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 # Region, [dk1, dk2] + advanced: | + type: template + template: energinet + 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) +params: + - name: region + example: dk1 + default: + choice: ['dk1', 'dk2'] + unit: + description: Region + 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 4f34b5811..000000000 --- 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 2b24b007d..000000000 --- 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 000000000..78a99fef3 --- /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: # 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: # 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 # Intervall, optional +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + 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: Anbieter + 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: Intervall + 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 2cc262704..000000000 --- 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 000000000..b005cd47a --- /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: # 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: # 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) +params: + - name: securitytoken + example: + default: + choice: [] + unit: + 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 + - name: domain + example: BZN|DE-LU + default: + choice: [] + unit: + description: Domain + 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 24d1a1d5a..000000000 --- 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 000000000..16089ba81 --- /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 # Intervall, 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: Intervall + 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 b15ecb6b5..000000000 --- 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 000000000..18d8e934b --- /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 # 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 # 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) +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: Gebotszone + help: siehe 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 000000000..b0a07aa28 --- /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 1cd247350..000000000 --- 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 000000000..de5a82f1b --- /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 eb503a244..000000000 --- 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 000000000..a02a13d4e --- /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: # 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: Postleitzahl + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + 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/gr\303\274nstromindex_0.yaml" "b/templates/release/de/tariff/gr\303\274nstromindex_0.yaml" deleted file mode 100644 index 0a02c63f6..000000000 --- "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 000000000..b166be3f6 --- /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 # 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: Region + 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: 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/ngeso_0.yaml b/templates/release/de/tariff/ngeso_0.yaml deleted file mode 100644 index 42c27e82d..000000000 --- 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 000000000..512a05db2 --- /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 # 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 # 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) +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: Region + help: + advanced: false + optional: true + - name: currency + example: + default: EUR + choice: ['DKK', 'EUR', 'NOK', 'PLN', 'RON', 'SEK'] + unit: + description: Währung + 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 c297312d4..000000000 --- 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 dd0bb8b35..000000000 --- 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 000000000..217ef09b1 --- /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: # API Key + accountNumber: X-XXXXXXXX # Kundennummer, Nur erforderlich, wenn mehrere Konten vorhanden sind. (optional) +params: + - name: apiKey + example: + default: + choice: [] + unit: + description: API Key + help: + advanced: false + optional: false + - name: accountNumber + example: X-XXXXXXXX + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..02614270b --- /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 # 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: Tarifcode + 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: 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 + - name: directDebit + example: + default: true + choice: [] + unit: + 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/octopus-productcode_0.yaml b/templates/release/de/tariff/octopus-productcode_0.yaml deleted file mode 100644 index 4b29cd671..000000000 --- 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 000000000..c2b533629 --- /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 # Intervall, 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: Intervall + 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 bed9c12b2..000000000 --- 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 000000000..ad9764e56 --- /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 # 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: Client ID + help: + advanced: false + optional: false + - name: clientsecret + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a + default: + choice: [] + unit: + description: Client Secret + help: + advanced: false + optional: false + - name: contract + example: 100523456 + default: + choice: [] + unit: + 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/ostrom_0.yaml b/templates/release/de/tariff/ostrom_0.yaml deleted file mode 100644 index ece29a402..000000000 --- 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 000000000..68693fbf9 --- /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 fda1ea56f..000000000 --- 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 000000000..5703b7236 --- /dev/null +++ b/templates/release/de/tariff/smartenergy-smartcontrol.yaml @@ -0,0 +1,46 @@ +template: smartenergy +product: + identifier: smartenergy-smartcontrol + brand: SmartEnergy + description: smartCONTROL + group: Dynamischer Strompreis +countries: ["AT"] +requirements: ["skiptest"] +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 e98a68ae1..000000000 --- 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 000000000..53dbc89b7 --- /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: # API Token + advanced: | + type: template + template: solcast + site: # Ressource ID deiner Anlage + 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: Ressource ID deiner Anlage + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: API Token + help: + advanced: false + optional: false + - name: from + example: + default: + choice: [] + unit: + description: Startzeit + help: Startzeit der Datenabrufe, Angabe in vollen Stunden, z.B "6" + advanced: true + optional: true + - name: to + example: + default: + choice: [] + unit: + description: Endzeit + help: Endzeit der Datenabrufe, Angabe in vollen Stunden, z.B "20" + advanced: true + optional: true + - name: interval + example: + default: 3h + choice: [] + unit: + description: Intervall + 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 bc6c77802..000000000 --- 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 000000000..89397dd2b --- /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 # 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 # 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) +params: + - name: contractid + example: ffffffff-4444-6666-2222-aaaaaabbbbbb + default: + choice: [] + unit: + description: Vertragsnummer + 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: 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 + - 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 dfb3bc0b5..000000000 --- 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 000000000..baa6e5f0b --- /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 # 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 # 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) +params: + - name: token + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + default: + choice: [] + unit: + description: API Token + help: + advanced: false + optional: false + - name: homeid + example: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c + default: + choice: [] + unit: + description: Home ID + 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 de3c6130d..000000000 --- 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 000000000..3ce4bf4bc --- /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 # Intervall, 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: Intervall + 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 83fd4926b..000000000 --- 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 000000000..90295382a --- /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, 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) + 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 + 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 + 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 5e0497c25..000000000 --- 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 000000000..f2e57177a --- /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, 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) + 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 + 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 + 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 577105d57..000000000 --- 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 000000000..4363633d4 --- /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: # Captcha Token + 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: # 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, 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) + 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: Captcha 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 + 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 + 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 fc093dab6..000000000 --- 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 520342357..000000000 --- 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 000000000..d1a6647c7 --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 dc4ce6ca3..000000000 --- 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 9e6a57b1d..000000000 --- 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 000000000..bfcbd4ac9 --- /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, 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) + 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 + 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 + 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 d6eb64909..000000000 --- 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 000000000..1357465e1 --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 d58c9674f..000000000 --- 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 f02d4c5b4..000000000 --- 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 000000000..7aa31bf11 --- /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: # 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: # 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, 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) +params: + - name: akey + example: + default: + choice: [] + unit: + description: API Key + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Token + 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 + 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 + 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 805d25332..000000000 --- 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 000000000..f249d551b --- /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: # 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: # 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, 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) + 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: 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 + - 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 + 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 + 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 f21faac87..000000000 --- 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 3ab9d0792..000000000 --- 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 387e97b4c..000000000 --- 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 32d7605e3..000000000 --- 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 000000000..092cea2fd --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 000000000..bcb857f9a --- /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, 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) +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 + 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 + 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 000000000..3be9bc3a0 --- /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, 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) + 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 + 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 + 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 8d6e6900a..000000000 --- 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 cdc3a16d9..000000000 --- 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 000000000..dedf3f6e6 --- /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 + 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 + 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, 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) + 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 + help: einschliesslich ioBroker.simple-api Port + 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 + 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 + 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 000000000..16681dce4 --- /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, 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) +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 + 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 + 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 4adfbf8ca..000000000 --- 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 000000000..e34ef09e2 --- /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: # 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: # 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, 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) + 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: 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 + - 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 + 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 + 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 000000000..e76bfccef --- /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, 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) + 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 + 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 + 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 578058314..000000000 --- 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 000000000..1b5b52cd1 --- /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 # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token + 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 # 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, 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) + 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: Region + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 095d73709..000000000 --- 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 000000000..30bb16d7f --- /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, 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) + 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 + 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 + 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 000000000..c26302b1c --- /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, 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) +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 + 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 + 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 4d010db65..000000000 --- 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 801c70bb8..000000000 --- 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 000000000..ae5d38269 --- /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: # Captcha Token + 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: # 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, 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) + 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: Captcha 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 + 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 + 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 556ef1206..000000000 --- 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 000000000..7109aa57e --- /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, 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) + 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 + 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 + 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 555893907..000000000 --- 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 000000000..648f16b23 --- /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, 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) + 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 + 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 + 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 7375f4a67..000000000 --- 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 000000000..5d98cf22a --- /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, 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) + 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 + 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 + 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 000000000..8754483d7 --- /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, 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) + 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 + 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 + 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 6f2817324..000000000 --- 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 000000000..6561f215e --- /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 d4de38270..000000000 --- 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 3bbe09e4e..000000000 --- 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 000000000..ed5b73d19 --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 b4bc929c8..000000000 --- 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 000000000..50602ff21 --- /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: # Vehicle ID + 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: # 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, 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 + 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: Vehicle ID + 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 + 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 + 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: Server + 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 9e566a959..000000000 --- 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 000000000..250e4d9d2 --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 d787bcc5a..000000000 --- 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 000000000..bfffeb4bb --- /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, 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) + 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 + 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 + 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 6263d897f..000000000 --- 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 000000000..cc6deb0e2 --- /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 # 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 + 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, 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, Kann zu erhöhter Entladung der 12V-Batterie führen. (optional) +params: + - name: url + example: http://192.0.2.2 + default: + choice: [] + unit: + description: URL + 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 + 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 + 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: 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 new file mode 100644 index 000000000..d92a7b936 --- /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, 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) + 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 + 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 + 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 561d97471..000000000 --- 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 000000000..3a4c4da31 --- /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, 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) + 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 + 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 + 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 000000000..4b671dfae --- /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, 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) + 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 + 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 + 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 f33ff938d..000000000 --- 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 000000000..2185dfe81 --- /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, 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) + 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 + 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 + 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 000000000..cfef86b93 --- /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, 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) + 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 + 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 + 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 000000000..5e400ec2e --- /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 # Region, [EMEA, APAC, NORAM] + accessToken: # Access token + refreshToken: # Refresh token + 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 # 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, 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) + 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: Region + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 db5745bf0..000000000 --- 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 2aaeff5c2..000000000 --- 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 000000000..31a8aef37 --- /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, 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, 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, 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) +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: URL + 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 + 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 + 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 5f4093073..000000000 --- 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 000000000..0c931612b --- /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: # 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: # 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, 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 # 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 + 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: Client ID + help: von [Tesla Developer App](https://developer.tesla.com/dashboard). + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: Access token + help: von [myteslamate.com](https://app.myteslamate.com/). + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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: 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 + - name: proxyToken + example: + default: + choice: [] + unit: + 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 + - 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 35fd50304..000000000 --- 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 000000000..f2100f80b --- /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 # URL + 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 # 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, 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) +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: URL + 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 + 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 + 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 3d9e7e1a9..000000000 --- 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 000000000..4e9a7bfb7 --- /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, 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) +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 + 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 + 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 a15ba084e..000000000 --- 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 000000000..cceb61077 --- /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, 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) +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 + 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 + 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 2ad484f0b..000000000 --- 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 000000000..e8cd6a7fe --- /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, 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) + 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 + 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 + 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 90c811706..000000000 --- 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 000000000..e8ea88259 --- /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, 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) + 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 + 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 + 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 bda3aba39..000000000 --- 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 000000000..1157d4ccd --- /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, 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) + 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 + 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 + 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 a6e03e48d..000000000 --- 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 000000000..5293520ff --- /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, 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, 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, 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) +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: VCC API Key + help: aus [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientId + example: + default: + choice: [] + unit: + description: Client ID + help: aus [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientSecret + example: + default: + choice: [] + unit: + description: Client Secret + help: aus [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: redirectUri + example: + default: + choice: [] + unit: + 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 + 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 + 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 + 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 000000000..6a80abd75 --- /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, 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) +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 + 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 + 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 2a566108f..000000000 --- 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 f44aba986..000000000 --- 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 000000000..39cfb45ff --- /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, 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) + 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 + 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 + 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 e13f599db..000000000 --- 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 3eda50aea..000000000 --- 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 c7bd4139c..000000000 --- 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 85c342294..000000000 --- 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 11589d88e..000000000 --- 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 e427cae71..000000000 --- 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 ecab3168e..000000000 --- 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 000000000..e2c39fd72 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..8d9a0766f --- /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: Modbus Type + 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 537b90cf5..000000000 --- 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 000000000..6ca1d7a53 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..0a49ad871 --- /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: Modbus Type + 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 000000000..94a685278 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..3136c6146 --- /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: Modbus Type + 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 59227336b..000000000 --- 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 000000000..9aaa9791c --- /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: Modbus Type + 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 000000000..0999ff412 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..733c3bbdc --- /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: Modbus Type + 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 000000000..bc23a8849 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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_0.yaml b/templates/release/en/charger/abl_0.yaml deleted file mode 100644 index 31dd8d81e..000000000 --- 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 5988bc7e0..000000000 --- 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 ab0c39bbb..000000000 --- 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 47636a734..000000000 --- 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 cbe0ba9ce..000000000 --- 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 34806ba75..000000000 --- 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 000000000..7285fd8fb --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..325130e81 --- /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: Modbus Type + 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 66eddbbd3..000000000 --- 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 000000000..b7f9dbbd8 --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..37d2916ba --- /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: Modbus Type + 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 000000000..8b63c918d --- /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: Modbus Type + 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 000000000..475d1775c --- /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: Modbus Type + 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 653775617..000000000 --- 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 cdbf11c5f..000000000 --- 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 cbb059989..000000000 --- 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 b8e74f2bb..000000000 --- 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 3a2dc3806..000000000 --- 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 000000000..d90ffbdd4 --- /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: Modbus Type + 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 000000000..dd614b25c --- /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: Modbus Type + 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 000000000..7e24581fb --- /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: Modbus Type + 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 000000000..7f88aeb8c --- /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: Modbus Type + 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 98a6dd4e9..000000000 --- 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 630984a20..000000000 --- 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 000000000..e75379d04 --- /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 000000000..bc76a79c2 --- /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: Modbus Type + 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 000000000..2ebb7208a --- /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 000000000..2fc5f7a83 --- /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 000000000..724569cd7 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..b0456088d --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..c43974a14 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..0a0645ded --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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/avm-fritzdect.yaml b/templates/release/en/charger/avm-fritzdect.yaml new file mode 100644 index 000000000..3c8e9c68c --- /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 000000000..1d6402205 --- /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: Modbus Type + 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 000000000..80fbebe43 --- /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: Modbus Type + 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 2c01dcae7..000000000 --- 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 bbdfa9886..000000000 --- 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 a47eafeb6..000000000 --- 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 ccdf4e27a..000000000 --- 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 53d289046..000000000 --- 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 d9f0a2e1d..000000000 --- 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 57ae464d1..000000000 --- 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 128564141..000000000 --- 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 db30a4e6f..000000000 --- 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 74181a627..000000000 --- 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 ac29abac3..000000000 --- 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 a0e96d6a6..000000000 --- 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 64465aaeb..000000000 --- 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 d6b1df0bb..000000000 --- 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 8a3ad1cce..000000000 --- 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 9bf575baa..000000000 --- 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 000000000..bc0a3fc42 --- /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: Modbus Type + 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 000000000..924d96183 --- /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: Modbus Type + 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 0fcea4a6c..000000000 --- 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 d4b1a6613..000000000 --- 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 154f62841..000000000 --- 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 0722cf521..000000000 --- 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 000000000..80f046763 --- /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: Modbus Type + 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 000000000..dabf1c238 --- /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: # 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: Token + 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 000000000..3f81ede88 --- /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 # Watchdog, 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: 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 new file mode 100644 index 000000000..62cb2d515 --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..90d2f501d --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..f905d2259 --- /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: # 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: Token + 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 000000000..7cbb9cb5c --- /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 000000000..f75a0ee62 --- /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 1321c0f64..000000000 --- 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 bf6800e7c..000000000 --- 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 000000000..433aaaa72 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..18d2ca456 --- /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: Modbus Type + 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 000000000..d12fab794 --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..1dba6f8a4 --- /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: Modbus Type + 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 000000000..c5fc0eb7e --- /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: Modbus Type + 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 000000000..300efaa1c --- /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 000000000..dda022828 --- /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 000000000..dfea74d4a --- /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 000000000..22daf02fd --- /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 000000000..b03d1921d --- /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 000000000..fa69fc587 --- /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: Modbus Type + 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 7a916c80e..000000000 --- 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 1f3f7c2ee..000000000 --- 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 000000000..2ce0f64a4 --- /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 000000000..a68a2feb7 --- /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: Modbus Type + 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 a1c5a4abe..000000000 --- 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 000000000..f1fc8c704 --- /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: Modbus Type + 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 000000000..928dc34aa --- /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: Modbus Type + 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 000000000..43189d2fe --- /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: Modbus Type + 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 000000000..26a6da010 --- /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: Modbus Type + 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 90af37b2c..000000000 --- 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 de38935e8..000000000 --- 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 df6bde5e5..000000000 --- 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 f85b44f55..000000000 --- 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 000000000..9cf0000f7 --- /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 edc88f9da..000000000 --- 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 000000000..328ea1207 --- /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: Modbus Type + 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 000000000..c31520291 --- /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: Modbus Type + 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 000000000..b9e30c8b0 --- /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: Modbus Type + 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 000000000..eb0d2bcaa --- /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______ # 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: # 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: + 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: Charger serial number + 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: 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 new file mode 100644 index 000000000..8297dd763 --- /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______ # 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: # 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: + 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: Charger serial number + 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: 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 new file mode 100644 index 000000000..9082e0549 --- /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______ # 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: # 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: + 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: Charger serial number + 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: 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 new file mode 100644 index 000000000..8160c69ae --- /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______ # 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: # 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: + 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: Charger serial number + 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: 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_0.yaml b/templates/release/en/charger/easee_0.yaml deleted file mode 100644 index 069882a82..000000000 --- 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 f86f3338a..000000000 --- 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 120490109..000000000 --- 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 1d5206c7c..000000000 --- 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 000000000..0eda4cf81 --- /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: Modbus Type + 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 000000000..f7364ed64 --- /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 000000000..dd00ca68f --- /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 000000000..c95ccdd49 --- /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 000000000..257f0d1cd --- /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: Modbus Type + 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 000000000..6c58917f3 --- /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: Modbus Type + 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 000000000..3792c8bc4 --- /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 acb2c68ea..000000000 --- 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 000000000..7f10785ee --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..e060d9ed5 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..d34574978 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..ad230b043 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..3fe1f1c1f --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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/elli-2_0.yaml b/templates/release/en/charger/elli-2_0.yaml deleted file mode 100644 index f78d334f0..000000000 --- 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 5f08a8d94..000000000 --- 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 e9b9e67aa..000000000 --- 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 635b665fd..000000000 --- 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 b7c67cad1..000000000 --- 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 959332f6b..000000000 --- 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 dd09d5469..000000000 --- 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 bab7de0f9..000000000 --- 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 b11eaf535..000000000 --- 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 7e5120f12..000000000 --- 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 47eb5ee0e..000000000 --- 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 d445d4b5f..000000000 --- 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 000000000..7506b8745 --- /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 000000000..f131caa4f --- /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 000000000..82c9aa2b8 --- /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 000000000..b8682237b --- /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 000000000..f67b55a9e --- /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 2f6255db4..000000000 --- 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 736c7f770..000000000 --- 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 846d2c813..000000000 --- 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 031ebd5a3..000000000 --- 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 b23696370..000000000 --- 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 b14cd592b..000000000 --- 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 6f6a63208..000000000 --- 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 92c0fe191..000000000 --- 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 cd3f1dba8..000000000 --- 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 7fe6493a4..000000000 --- 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 000000000..e7fc0ebe9 --- /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 07b28709a..000000000 --- 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 000000000..8484ecc50 --- /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: Modbus Type + 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 5735a3495..000000000 --- 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 38ab23fcc..000000000 --- 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 9b4bc52c1..000000000 --- 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 4f4a563f8..000000000 --- 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 000000000..39fa64dc5 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..8e76d4283 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..977b1804d --- /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: Modbus Type + 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 000000000..856663b82 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..e65d14cd9 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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/eprowallbox_0.yaml b/templates/release/en/charger/eprowallbox_0.yaml deleted file mode 100644 index 9f74cf8d5..000000000 --- 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 000000000..d09e4bf09 --- /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: Modbus Type + 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 000000000..0e90d5703 --- /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 1752e022f..000000000 --- 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 000000000..65b432fb7 --- /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 000000000..e70651458 --- /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 4df177382..000000000 --- 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 9bad6e2a3..000000000 --- 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 000000000..698e02e66 --- /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 # 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 # Meter ID, optional + connector: 1 # Connector number, For charging stations with multiple connectors. Counting starts at 1 for the first connector. (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 + 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: Meter ID + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + 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: 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/evbox-livo.yaml b/templates/release/en/charger/evbox-livo.yaml new file mode 100644 index 000000000..89da690d2 --- /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 000000000..a7f83a526 --- /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: Modbus Type + 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 4f2a93b26..000000000 --- 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 caf6f2072..000000000 --- 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 000000000..e0e018060 --- /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 5795fa06d..000000000 --- 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 000000000..6eb60d4fe --- /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: Modbus Type + 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 000000000..540f8046b --- /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: Modbus Type + 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 000000000..28c58aadd --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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/fritzdect_0.yaml b/templates/release/en/charger/fritzdect_0.yaml deleted file mode 100644 index 5815b41e4..000000000 --- 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 000000000..3498f8bc7 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..483836c62 --- /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: Modbus Type + 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 000000000..a01f95280 --- /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: Modbus Type + 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 000000000..d396cb53a --- /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: Modbus Type + 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 000000000..3c22075bf --- /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: Modbus Type + 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 cd1329080..000000000 --- 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 1bb2714a3..000000000 --- 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 000000000..4b6a66be0 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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-gemini.yaml b/templates/release/en/charger/go-e-charger-gemini.yaml new file mode 100644 index 000000000..34d064674 --- /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 000000000..bb120299b --- /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 000000000..b1c443844 --- /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 000000000..68fda4ef7 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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.yaml b/templates/release/en/charger/go-e-charger-pro.yaml new file mode 100644 index 000000000..ddabf61e4 --- /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 000000000..80bad9b38 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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.yaml b/templates/release/en/charger/go-e-charger-v3.yaml new file mode 100644 index 000000000..537e188ef --- /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 2368290fc..000000000 --- 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 7ab41af35..000000000 --- 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 52adab157..000000000 --- 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 fe0499ca0..000000000 --- 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 3806244bc..000000000 --- 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 000000000..6bd15a728 --- /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 000000000..a3a08a750 --- /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 000000000..82d12254b --- /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 386a0bf0b..000000000 --- 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 aaf632a2e..000000000 --- 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 811cd8410..000000000 --- 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 a316c5dfd..000000000 --- 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 d567cef27..000000000 --- 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 244481cd2..000000000 --- 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 000000000..7ea04dd79 --- /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: Modbus Type + 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 04e1da686..000000000 --- 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 5f910f2d2..000000000 --- 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 360a58cf4..000000000 --- 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 863e1833e..000000000 --- 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 000000000..9e626fdd0 --- /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: Modbus Type + 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 000000000..d6c99a979 --- /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: Modbus Type + 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 f709745da..000000000 --- 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 387c70b2f..000000000 --- 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 000000000..b0f58c8c8 --- /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 960aee862..000000000 --- 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 000000000..33fb517e5 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..3e395ea6d --- /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, 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, 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, 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) +params: + - name: host + example: 192.0.2.2 + default: + choice: [] + unit: + description: IP address or hostname + help: + advanced: false + optional: false + - name: port + example: BidCos-Wired=2000, BidCos-RF=2001, HmIP=2010 + default: 2010 + choice: [] + unit: + description: XML-RPC server port number + 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: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM=2 + default: 6 + choice: [] + unit: + description: Meter channel number + help: Homematic meter channel number like shown in the CCU web user interface. + advanced: true + optional: false + - name: switchchannel + example: HMIP-PSM=3, HMIP-FSM+HMIP-FSM16=2, HM=1 + default: 3 + choice: [] + unit: + description: Switch/Actor channel number + 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 + 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 2b9e3c310..000000000 --- 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 000000000..569127140 --- /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 9f251ecda..000000000 --- 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 000000000..52f0bb543 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..ba66d59ea --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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/ichargecion_0.yaml b/templates/release/en/charger/ichargecion_0.yaml deleted file mode 100644 index b17e5e89d..000000000 --- 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 2e266ef1b..000000000 --- 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 000000000..f6260fba9 --- /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: Modbus Type + 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 690f1b577..000000000 --- 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 000000000..004843e2b --- /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: Modbus Type + 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 805ac61c0..000000000 --- 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 628cd3218..000000000 --- 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 a35d5b198..000000000 --- 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 000000000..c483687e5 --- /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 000000000..9f2270832 --- /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: Modbus Type + 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 000000000..50f42cfaf --- /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: # 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: Token + 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 000000000..898362ebb --- /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: Modbus Type + 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 000000000..17b7afa7a --- /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: Modbus Type + 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 000000000..bfe949479 --- /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: Modbus Type + 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 000000000..986a01f8f --- /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: Modbus Type + 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 000000000..5455e1e5f --- /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: Modbus Type + 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 000000000..7017c59b8 --- /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: Modbus Type + 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 000000000..4fd1f524d --- /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: Modbus Type + 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 000000000..f085038fa --- /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: Modbus Type + 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 000000000..44f606283 --- /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: Modbus Type + 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 000000000..aa133df2a --- /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: Modbus Type + 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 000000000..1bdebf15d --- /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: Modbus Type + 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 b84fbdf3a..000000000 --- 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 db52e7541..000000000 --- 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 fe52ef144..000000000 --- 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 c6b9f3a2b..000000000 --- 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 fba8368ca..000000000 --- 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 11b25ed69..000000000 --- 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 6f88b5d7a..000000000 --- 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 000000000..0d4de2b51 --- /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 # Watchdog, 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: Watchdog + 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 9dc3f046d..000000000 --- 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 8612a402f..000000000 --- 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 000000000..64d212868 --- /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 000000000..1ca33876e --- /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: Modbus Type + 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 000000000..5de347ad3 --- /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: Modbus Type + 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 eb69e1c9f..000000000 --- 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 000000000..0093c1e93 --- /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: Modbus Type + 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 000000000..4d9ce8af2 --- /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: Modbus Type + 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 000000000..17b060aef --- /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 # Watchdog, 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: Watchdog + 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 ecdbe2817..000000000 --- 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 d99dcf652..000000000 --- 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 958b3a075..000000000 --- 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 000000000..75ed42b7f --- /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: Modbus Type + 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 7b4d9a3c8..000000000 --- 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 9a3e13a73..000000000 --- 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 ee3c4312a..000000000 --- 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 1ae8eb3f6..000000000 --- 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 3285d2c7f..000000000 --- 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 a69f1eeff..000000000 --- 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 5a1ed904a..000000000 --- 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 37360d2c3..000000000 --- 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 60723f68a..000000000 --- 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 b798ad00b..000000000 --- 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 586a745b8..000000000 --- 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 000000000..65dd31808 --- /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: Modbus Type + 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 000000000..7e829fb74 --- /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: Modbus Type + 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 000000000..ed13de10f --- /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: Modbus Type + 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 000000000..b0b25cbee --- /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: Modbus Type + 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 000000000..7d6e15501 --- /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: Modbus Type + 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 000000000..3288a9547 --- /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: Modbus Type + 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 000000000..7cb5aed88 --- /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: Modbus Type + 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 000000000..daedc6723 --- /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: Modbus Type + 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 000000000..3474ca33d --- /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: Modbus Type + 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 9caa15c41..000000000 --- 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 8f0a6638b..000000000 --- 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 2d1a4ff2b..000000000 --- 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 000000000..4b9c44d72 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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-hcc3_0.yaml b/templates/release/en/charger/mennekes-hcc3_0.yaml deleted file mode 100644 index 327f8b99e..000000000 --- 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 dbcb5fe2d..000000000 --- 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 000000000..147cc0a13 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..d5a49285c --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..594db4164 --- /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: Modbus Type + 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 000000000..77775768b --- /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 source, [1, 2, 3] (optional) + scale: 1 # Scale factor for power limit, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperature source + 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 000000000..1ceb501af --- /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 source, [1, 2, 3] (optional) + scale: 1 # Scale factor for power limit, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: tempsource + example: + default: 1 + choice: ['1', '2', '3'] + unit: + description: Temperature source + 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 000000000..fb021fd3f --- /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 3dc677c7a..000000000 --- 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 000000000..79a58e3ca --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..4a1eb5363 --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 9e415a9ef..000000000 --- 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 000000000..f240d0b92 --- /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: # MAC Address + 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: MAC Address + 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 5a4d0e727..000000000 --- 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 000000000..30f6889d7 --- /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 # Phase Switching enabled, Extended feature "Phase Switching" must be activated in the NRGKick app. (optional) +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: phases1p3p + example: + default: false + choice: [] + unit: + description: Phase Switching enabled + help: 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 000000000..bb1946c94 --- /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: Modbus Type + 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 bf4300498..000000000 --- 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 b47bf8b17..000000000 --- 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 920581ce8..000000000 --- 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 000000000..6a32a552b --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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/ocpp-abb-tac_0.yaml b/templates/release/en/charger/ocpp-abb-tac_0.yaml deleted file mode 100644 index 2571c9f71..000000000 --- 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 873a13c83..000000000 --- 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 48a737e75..000000000 --- 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 f9650e62b..000000000 --- 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 989176a19..000000000 --- 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 0883320b1..000000000 --- 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 6a545ff07..000000000 --- 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 c68ca7e43..000000000 --- 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 c0240ecde..000000000 --- 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 e86a3af3c..000000000 --- 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 e8184d642..000000000 --- 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 73b72693b..000000000 --- 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 c0a3563bc..000000000 --- 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 97e94949e..000000000 --- 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 655a212ef..000000000 --- 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 fd69e0665..000000000 --- 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 891cc1b2d..000000000 --- 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 0806f056e..000000000 --- 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 c37df2d32..000000000 --- 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 2e8f02d6a..000000000 --- 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 bfd7917b3..000000000 --- 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 3fa3cec78..000000000 --- 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 b76ac80dc..000000000 --- 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 166693cde..000000000 --- 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 4b206edb2..000000000 --- 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 8bf16e858..000000000 --- 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 b56159225..000000000 --- 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 079606675..000000000 --- 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 d8e731b40..000000000 --- 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 218405b29..000000000 --- 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 d569eefdd..000000000 --- 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 1350e2315..000000000 --- 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 6aac28490..000000000 --- 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 79286e348..000000000 --- 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 2cfe10fc0..000000000 --- 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 86d044dcd..000000000 --- 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 30ff13d05..000000000 --- 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 711a95e83..000000000 --- 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 2c7cbd465..000000000 --- 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 000000000..16a5e08cb --- /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 4cd324e5f..000000000 --- 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 c9af74d9c..000000000 --- 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 000000000..9430b2808 --- /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 3bc89ce0b..000000000 --- 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 000000000..bc3d7d67e --- /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 000000000..c064a4fd6 --- /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: Modbus Type + 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 c998e58f5..000000000 --- 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 000000000..892d0e5d1 --- /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: Modbus Type + 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 000000000..dc9d92daa --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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/pantabox_0.yaml b/templates/release/en/charger/pantabox_0.yaml deleted file mode 100644 index 1607b7c68..000000000 --- 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 000000000..c02f24095 --- /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 ad8becdfc..000000000 --- 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 000000000..84f56ce2c --- /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: Modbus Type + 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 000000000..2f2ac7031 --- /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: Modbus Type + 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 000000000..76a4aa2a2 --- /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: Modbus Type + 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 9f40acc89..000000000 --- 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 36fef832a..000000000 --- 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 2a2d62886..000000000 --- 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 b260dee1a..000000000 --- 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 211884ab4..000000000 --- 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 8723fb07a..000000000 --- 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 000000000..ebaada4ad --- /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: Modbus Type + 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 000000000..91c9681fd --- /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: Modbus Type + 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 000000000..32456f424 --- /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: Modbus Type + 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 000000000..902579d23 --- /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: Modbus Type + 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 000000000..eef29ed1c --- /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: Modbus Type + 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 000000000..90cf8bd00 --- /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: Modbus Type + 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 000000000..19e7d37fc --- /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: Modbus Type + 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 761efe9d6..000000000 --- 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 e47b91f6d..000000000 --- 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 4bad74acb..000000000 --- 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 848da2135..000000000 --- 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 049290939..000000000 --- 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 9129df752..000000000 --- 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 0d95d417e..000000000 --- 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 e1ccc8be9..000000000 --- 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 dfd172c24..000000000 --- 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 a1f93d491..000000000 --- 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 63128dfb4..000000000 --- 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 000000000..b394db8ed --- /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: # Token, API Token + identity: AA123456 # Charger identity + advanced: | + type: template + template: plugchoice + token: # Token, API Token + identity: AA123456 # Charger identity + connector: 1 # Connector ID +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + help: API Token + advanced: false + optional: false + - name: identity + example: AA123456 + default: + choice: [] + unit: + description: Charger identity + help: + advanced: false + optional: false + - name: connector + example: 1 + default: 1 + choice: [] + unit: + description: Connector ID + help: + 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 4a13f6125..000000000 --- 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 694b97a24..000000000 --- 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 e1d7dadb6..000000000 --- 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 000000000..6af404458 --- /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 000000000..0fd67cdd1 --- /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 000000000..695ea88a5 --- /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 9b9e7327a..000000000 --- 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 000000000..d4df70936 --- /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: Modbus Type + 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 b663d3b0e..000000000 --- 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 a302f13f8..000000000 --- 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 4bcd02ce8..000000000 --- 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 44d13e993..000000000 --- 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 000000000..fa1efec00 --- /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: Modbus Type + 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 000000000..a94a49a84 --- /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: Modbus Type + 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 000000000..8dcd17f27 --- /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: Modbus Type + 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 000000000..dba6e8974 --- /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: Modbus Type + 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 3b68b0218..000000000 --- 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 000000000..b2edd2796 --- /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 d9836d733..000000000 --- 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 000000000..80ea8dcec --- /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: Modbus Type + 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 000000000..45f8b6972 --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..095a26c78 --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..13dd023eb --- /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: Modbus Type + 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 080654a25..000000000 --- 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 000000000..f3f3b77e2 --- /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: Modbus Type + 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 000000000..3fa08b927 --- /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: Modbus Type + 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 000000000..8369de974 --- /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: Modbus Type + 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 000000000..6845a753a --- /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 # Channel, 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 # 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) + 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: Channel + 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 000000000..f14470ad3 --- /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 # Channel, 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 # 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) + 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: Channel + 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 000000000..fc6c27294 --- /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 # Channel, 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 # 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) + 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: Channel + 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 000000000..673757551 --- /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 # Channel, 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 # 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) + 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: Channel + 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 ab11ba524..000000000 --- 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 000000000..827b7f6fa --- /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: Modbus Type + 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 000000000..de595b2a8 --- /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 000000000..7d3173f52 --- /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 000000000..d653e94f4 --- /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 000000000..64ba65c00 --- /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 000000000..4ed650dad --- /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 000000000..559330726 --- /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 000000000..cb4092d4d --- /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 a93e45eb9..000000000 --- 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 589cbc804..000000000 --- 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 4ef89c2ed..000000000 --- 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 000000000..c8e953c58 --- /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: Modbus Type + 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 000000000..98717b891 --- /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 b8c3cce0b..000000000 --- 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 000000000..5b36897a1 --- /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: Modbus Type + 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 000000000..f1985343e --- /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: Modbus Type + 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 dfb8f568e..000000000 --- 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 98a778749..000000000 --- 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 20940b0c1..000000000 --- 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 000000000..3e9988e3e --- /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 000000000..8aa2892f0 --- /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: Modbus Type + 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 000000000..dcd81a44a --- /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: Modbus Type + 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 000000000..a503571e0 --- /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: Modbus Type + 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 000000000..79e55c1b5 --- /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: Modbus Type + 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 4e86a084b..000000000 --- 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 f8193b85d..000000000 --- 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 fed9fa335..000000000 --- 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 000000000..c36cbe754 --- /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: Modbus Type + 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 000000000..938c861ce --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..610b97a91 --- /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: Modbus Type + 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 84322afc6..000000000 --- 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 13687bf67..000000000 --- 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 5b40e65ca..000000000 --- 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 000000000..daf5faba0 --- /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 a3526d90b..000000000 --- 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 000000000..424187bf6 --- /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: Modbus Type + 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 000000000..be218ebce --- /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: Modbus Type + 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 000000000..807a61245 --- /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 000000000..743ead340 --- /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 # 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... + 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: 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/tessie_0.yaml b/templates/release/en/charger/tessie_0.yaml deleted file mode 100644 index d2cb6b952..000000000 --- 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 000000000..fad2eede5 --- /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: Modbus Type + 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 000000000..09dce1a79 --- /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: # Energy manager MQTT topic, WEM Firmware v2 required. (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: # 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: + - 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: Energy manager MQTT topic + help: WEM Firmware v2 required. + 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 000000000..ced63797e --- /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: # Energy manager MQTT topic, WEM Firmware v2 required. (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: # 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: + - 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: Energy manager MQTT topic + help: WEM Firmware v2 required. + 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 000000000..a05145462 --- /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 000000000..4703dafd3 --- /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 368aaab1d..000000000 --- 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 4ff2ba96c..000000000 --- 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 72d17458a..000000000 --- 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 b1809f339..000000000 --- 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 000000000..210a80b2d --- /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 000000000..e0626f612 --- /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 97097a9d0..000000000 --- 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 1518c57a4..000000000 --- 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 f7ad76713..000000000 --- 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 000000000..1d4657116 --- /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: Modbus Type + 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 000000000..2c5896981 --- /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 000000000..f90047a5d --- /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 # Region, [DE, AT] (optional) + zone: # Boost zone ID, optional + setpoint: # Boost temperature, 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: Region + help: + advanced: false + optional: true + - name: zone + example: + default: + choice: [] + unit: + description: Boost zone ID + help: + advanced: false + optional: true + - name: setpoint + example: + default: + choice: [] + unit: + description: Boost temperature + help: + 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 40e7150b1..000000000 --- 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 348a24a05..000000000 --- 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 000000000..2af0da46f --- /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: Modbus Type + 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 000000000..3393b21dc --- /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: Modbus Type + 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 710dda58f..000000000 --- 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 bd463fd75..000000000 --- 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 0d3b82ca8..000000000 --- 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 0d31d81d3..000000000 --- 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 d80fb51d9..000000000 --- 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 000000000..6cdc5748b --- /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: Modbus Type + 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 000000000..741728cee --- /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: Modbus Type + 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 2ec17a214..000000000 --- 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 7f7b7ea5b..000000000 --- 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 000000000..b501aa35c --- /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 d89be0f22..000000000 --- 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 000000000..063c22860 --- /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: Modbus Type + 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 000000000..816f5858e --- /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 000000000..c4b8c5ae9 --- /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 000000000..e4d74d159 --- /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 000000000..cb40c0ecc --- /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 000000000..2d31b6467 --- /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 000000000..cca658f6b --- /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: # 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: Token + 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: 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 new file mode 100644 index 000000000..722517502 --- /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: # 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: Token + 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: 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 new file mode 100644 index 000000000..ea2251686 --- /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: # 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: Token + 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: 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 new file mode 100644 index 000000000..ca00dfca6 --- /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: # 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: Token + 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: 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/volttime_0.yaml b/templates/release/en/charger/volttime_0.yaml deleted file mode 100644 index b653c5d3b..000000000 --- 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 b53f2b2cf..000000000 --- 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 407a9e389..000000000 --- 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 cf4e8fe61..000000000 --- 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 000000000..84fa3c97d --- /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: Modbus Type + 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 000000000..ae291e41b --- /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: Modbus Type + 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 000000000..ab7a5da04 --- /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: Modbus Type + 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 000000000..d7383fe14 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..a75d41b57 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..51285f365 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..c4ba8b3b7 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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-fw5_0.yaml b/templates/release/en/charger/wallbox-fw5_0.yaml deleted file mode 100644 index d0e207fca..000000000 --- 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 66520f7a1..000000000 --- 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 a71b771c8..000000000 --- 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 ca05a8dfd..000000000 --- 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 000000000..007378062 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..4b0ad9fb5 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..73bb44a9e --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..17ccbfafa --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..32d5c0860 --- /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: Modbus Type + 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 000000000..356d293af --- /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: Modbus Type + 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 000000000..96cc913a3 --- /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 c4e8ea002..000000000 --- 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 c547964af..000000000 --- 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 000000000..9ae542310 --- /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: Modbus Type + 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 000000000..208a9f860 --- /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 086e4ad63..000000000 --- "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 000000000..189637747 --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..916d60e9f --- /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 # Heating temperature boost (K), optional + advanced: | + type: template + template: luxtronik + + # Modbus TCP + modbus: tcpip + id: 1 + host: 192.0.2.2 # Hostname + port: 502 # Port + 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: Modbus Type + help: + advanced: false + optional: true + - name: heatoffset + example: '2.0' + default: '0.0' + choice: [] + unit: K + description: Heating temperature boost + help: + advanced: false + optional: true + - name: wwoffset + example: 8.5 + default: '0.0' + choice: [] + unit: K + description: Hot water temperature boost + 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 000000000..0e941c48c --- /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: # 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: ID + 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 000000000..0d5cc72ae --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..b123aba61 --- /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: # 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: ID + 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 000000000..a606a0dba --- /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: # 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: ID + 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 605150925..000000000 --- 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 a53e2bdea..000000000 --- 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 89ad73008..000000000 --- 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 000000000..50bff3aa7 --- /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 # Watchdog, 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: 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 new file mode 100644 index 000000000..1db243ed1 --- /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: # 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 + 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: 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 + example: evcc + default: + choice: [] + unit: + 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 + example: + default: 5m + choice: [] + unit: + description: Timeout for registration + help: Timeout for the registration of the charging point + advanced: true + optional: true + - name: meterinterval + example: + default: 10s + choice: [] + unit: + description: Transmission interval for meter values + help: Time interval for transmission of meter values (MeterValueSampleInterval) + 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: 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 new file mode 100644 index 000000000..b312970ff --- /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 # Delay, 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 # Delay, 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 # Delay, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Type + 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: Delay + 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 000000000..b5dbd4a4e --- /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: Modbus Type + 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 000000000..6e9fc7102 --- /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: Modbus Type + 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 8555cd10c..000000000 --- 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 000000000..dd8613f6d --- /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: Modbus Type + 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 000000000..9bd16074e --- /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: Modbus Type + 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 8b79787bc..000000000 --- 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 b876a4a35..000000000 --- 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 000000000..9f3078c41 --- /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: Modbus Type + 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 158d7b005..000000000 --- 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 000000000..0654e8308 --- /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: Modbus Type + 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 2d290b8d1..000000000 --- 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 000000000..be2082a37 --- /dev/null +++ b/templates/release/en/meter/alpha-ess-storion-smile.yaml @@ -0,0 +1,211 @@ +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 + - 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 + 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: Modbus Type + 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 000000000..48fd91e34 --- /dev/null +++ b/templates/release/en/meter/ampere-ampere-storagepro.yaml @@ -0,0 +1,207 @@ +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 + - 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 + - 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: Modbus Type + 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 000000000..5cd504828 --- /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: Modbus Type + 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 000000000..ff96f1a79 --- /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 270fae6e8..000000000 --- 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 000000000..3a0045439 --- /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 000000000..7dcb482c6 --- /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: Modbus Type + 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 000000000..3a4f510e3 --- /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: Modbus Type + 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 14bc06d87..000000000 --- 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 13119038a..000000000 --- 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 000000000..340b9051e --- /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: Modbus Type + 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 000000000..c1dfd9ed8 --- /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: Modbus Type + 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 000000000..8bd0c6b98 --- /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 addeb3d60..000000000 --- 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 000000000..70a3679c1 --- /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: Modbus Type + 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 000000000..be034a3b4 --- /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: Modbus Type + 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 000000000..0656c4299 --- /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: Modbus Type + 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 000000000..45b3fd48e --- /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: Modbus Type + 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 000000000..8006af0dd --- /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: Modbus Type + 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 000000000..146c7f950 --- /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: Modbus Type + 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 000000000..7828a4072 --- /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: Modbus Type + 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 000000000..57a0294ef --- /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: Modbus Type + 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 000000000..cc9894df2 --- /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: Modbus Type + 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 c7b87e0fc..000000000 --- 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 25b895e0b..000000000 --- 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 ae345cf0b..000000000 --- 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 bfa3faf84..000000000 --- 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 41616d459..000000000 --- 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 f888b1d08..000000000 --- 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 2e307a267..000000000 --- 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 c9e82d203..000000000 --- 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 20f08771e..000000000 --- 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 5d4dad42c..000000000 --- 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 c2d1600b6..000000000 --- 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 7235030cd..000000000 --- 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 335ed59fe..000000000 --- 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 000000000..7ef7b0ef9 --- /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 d371cb025..000000000 --- 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 000000000..f687b9608 --- /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 ba6a661a7..000000000 --- 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 000000000..fb0feffdf --- /dev/null +++ b/templates/release/en/meter/deye-3p-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Type + 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 000000000..9d7e02004 --- /dev/null +++ b/templates/release/en/meter/deye-hp3-hybrid-inverter.yaml @@ -0,0 +1,232 @@ +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 # Battery storage unit index, 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 # 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 + 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 # 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) + includegenport: # Treat GEN port as solar input, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Battery storage unit index + 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 d99d1696c..000000000 --- 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 71ed1480d..000000000 --- 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 295a5506a..000000000 --- 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 b51d2fc8e..000000000 --- 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 330b3dd9a..000000000 --- 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 aef8b4506..000000000 --- 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 02fbe72af..000000000 --- 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 8a119828b..000000000 --- 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 000000000..ca9436d71 --- /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: Modbus Type + 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 000000000..746820ee6 --- /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: Modbus Type + 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 7364fc120..000000000 --- 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 9983191da..000000000 --- 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 000000000..59b67a843 --- /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: Modbus Type + 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 b584ebb31..000000000 --- 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 b1959c296..000000000 --- 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 000000000..b9d80d1d6 --- /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 # Meter ID + - 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 # Meter ID +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: Meter ID + 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 1c3433ab4..000000000 --- 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 000000000..7785f404b --- /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 d446e15f9..000000000 --- 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 000000000..a0e6464cf --- /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: Modbus Type + 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 944659a79..000000000 --- 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 000000000..5965cb45c --- /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: # RSCP-Password + 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: # RSCP-Password + 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: # RSCP-Password + 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: # 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 + 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: # RSCP-Password + 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: # RSCP-Password + 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: RSCP-Password + 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 46c1417c3..000000000 --- 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 000000000..37a9ba732 --- /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: Modbus Type + 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 c523f2787..000000000 --- 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 000000000..cff5f62d9 --- /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: Modbus Type + 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 52e4d9b14..000000000 --- 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 17900c48e..000000000 --- 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 dc9eab47b..000000000 --- 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 000000000..a5d9c3679 --- /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: Modbus Type + 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 bbc7de94e..000000000 --- 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 000000000..dc8385803 --- /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: Modbus Type + 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 000000000..7470ba821 --- /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: Modbus Type + 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 c15d696c0..000000000 --- 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 dbc823ff7..000000000 --- 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 02e511569..000000000 --- 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 3086ab92f..000000000 --- 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 407eedce6..000000000 --- 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 000000000..6bf24e2e0 --- /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: # 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: # 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: # 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: # 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: # 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: # 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: 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 + - 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 80d13c73f..000000000 --- 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 4add4696f..000000000 --- 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 000000000..0092818ac --- /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 000000000..0902751e9 --- /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 000000000..c2061fc6b --- /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 # Watchdog, 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: Controllable battery component + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: Watchdog + 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 5e59afc06..000000000 --- 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 de82de19a..000000000 --- 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 f6b88aa5e..000000000 --- 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 000000000..a9af8da1a --- /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: Modbus Type + 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 000000000..09c26e856 --- /dev/null +++ b/templates/release/en/meter/foxess-h3-series-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Type + 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 000000000..77d10b669 --- /dev/null +++ b/templates/release/en/meter/foxess-h3-smart-series-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Type + 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 5882189e5..000000000 --- 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 f48056ee4..000000000 --- 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 b80de12f2..000000000 --- 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 000000000..db198241b --- /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 47a0293b9..000000000 --- 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 000000000..aa72871f9 --- /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 # 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 + 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: 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 + - 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 000000000..10040648e --- /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: Modbus Type + 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 000000000..e696dafc0 --- /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 # Battery configuration URI, Firmware starting with 1.36.5-1 requires /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 # Battery configuration URI, Firmware starting with 1.36.5-1 requires /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 # 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 + 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: 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-solarapi-v1_0.yaml b/templates/release/en/meter/fronius-solarapi-v1_0.yaml deleted file mode 100644 index 5dc266674..000000000 --- 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 000000000..f64a7c5f6 --- /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 # 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 + 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: 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 + - 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 000000000..59cc75f10 --- /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: Modbus Type + 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 000000000..1e986b0a4 --- /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: Modbus Type + 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 000000000..40a7fa71d --- /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: Modbus Type + 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 000000000..f84a81866 --- /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 675e63f6d..000000000 --- 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 f4a2cd4b5..000000000 --- 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 000000000..aee67434b --- /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 # Battery number, [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 # Battery number, [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 # Battery number, [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 # Battery number, [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 # Battery number, [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 # Battery number, [1, 2] (optional) + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip', 'udp'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: battery + example: + default: 1 + choice: ['1', '2'] + unit: + description: Battery number + 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 000000000..34fb7ade4 --- /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 3b2c762ed..000000000 --- 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 000000000..560792a7f --- /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: Modbus Type + 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 274712a35..000000000 --- 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 000000000..a772ccb28 --- /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: Modbus Type + 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 c380d6c51..000000000 --- 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 07502d8a5..000000000 --- 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 000000000..7690e0f7c --- /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: Modbus Type + 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 000000000..541899f73 --- /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, 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, 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 + 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, 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, 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 + 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, 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, 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 + 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: HMIP-PSM=6, HMIP-FSM+HMIP-FSM16=5, HM-ES-TX-WM=1 + default: 6 + choice: [] + unit: + 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 + - name: cache + example: 5m + default: 1s + choice: [] + unit: + 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/homematic_0.yaml b/templates/release/en/meter/homematic_0.yaml deleted file mode 100644 index 812c5e122..000000000 --- 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 000000000..79f94ccfa --- /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 8836bf782..000000000 --- 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 000000000..8dd5d424d --- /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 90e207dbd..000000000 --- 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 e2f3bfff5..000000000 --- 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 000000000..c270bc7f9 --- /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 + 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/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 000000000..317cc1bc1 --- /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 562663507..000000000 --- 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 6d8dcf604..000000000 --- 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 000000000..df2a19126 --- /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: Modbus Type + 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 a609847eb..000000000 --- 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 000000000..8bdab3942 --- /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 # Battery storage unit index, 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 # Battery storage unit index, 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 # Battery storage unit index, optional + capacity: 50 # Battery capacity (kWh), optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Battery storage unit index + 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 210607213..000000000 --- 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 000000000..1fcc53cae --- /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: Modbus Type + 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 000000000..309a11899 --- /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 # Battery storage unit index, 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 # Battery storage unit index, 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 # 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) +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Type + 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: Battery storage unit index + 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 cae3953e4..000000000 --- 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 000000000..fe39602cc --- /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 000000000..60cfc0dcb --- /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 e3c36326c..000000000 --- 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 2a7b54c2a..000000000 --- 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 000000000..0c1644d82 --- /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 000000000..2e15d54e9 --- /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: Modbus Type + 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 a72a94dd1..000000000 --- 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 000000000..8d6d1c8b8 --- /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 ab4bc3558..000000000 --- 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 000000000..f7919f6d0 --- /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: Modbus Type + 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 000000000..9f78ac1b4 --- /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: Modbus Type + 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 1c8d9b69f..000000000 --- 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 000000000..b0a9abd82 --- /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: Modbus Type + 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 8ac865893..000000000 --- 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 000000000..ace4a9581 --- /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: Modbus Type + 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 000000000..7fc8eb23c --- /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: Modbus Type + 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 94e1f0078..000000000 --- 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 a2d146cf9..000000000 --- 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 000000000..b858ce2e5 --- /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 000000000..6afda4ee6 --- /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 5966a3f24..000000000 --- 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 000000000..280f85e0e --- /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 20cdddb4b..000000000 --- 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 000000000..61e2452f7 --- /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 74ff42473..000000000 --- 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 c609239b4..000000000 --- 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 e8f305186..000000000 --- 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 000000000..b7a8f91dc --- /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 a30b9e2d4..000000000 --- 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 000000000..8892e5da6 --- /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 # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Watchdog + 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 000000000..61eeb04bc --- /dev/null +++ b/templates/release/en/meter/kostal-plenticore-hybrid.yaml @@ -0,0 +1,131 @@ +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 + watchdog: 60s # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Watchdog + 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 498bea513..000000000 --- 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 000000000..d5de69cf1 --- /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: Modbus Type + 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 000000000..fade7a04d --- /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: Modbus Type + 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 000000000..d1564d9f8 --- /dev/null +++ b/templates/release/en/meter/lg-ess-home-15.yaml @@ -0,0 +1,107 @@ +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, ID of the LG ESS HOME inverter. (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, ID of the LG ESS HOME inverter. (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, 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: Registration ID + help: 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 b7ad9634b..000000000 --- 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 000000000..cc436ef85 --- /dev/null +++ b/templates/release/en/meter/lg-ess-home-8-10.yaml @@ -0,0 +1,110 @@ +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, ID of the LG ESS HOME inverter. (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, ID of the LG ESS HOME inverter. (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, 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: Registration ID + help: 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 91bad0898..000000000 --- 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 000000000..43db43732 --- /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 1f06e4255..000000000 --- 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 000000000..38c294478 --- /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: Modbus Type + 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 000000000..ef06f3074 --- /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: Modbus Type + 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 000000000..e15b56d3d --- /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 # 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 # 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: Modbus Type + 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: 11 + default: 11 + choice: [] + unit: '%' + description: Minimum charge + help: Venus can only be discharged down to 11%. + 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: Maximum charge power + help: 2500W is the maximum for Venus. + advanced: true + optional: true + - name: work_mode_normal + example: + default: 1 + choice: [] + unit: + description: Work mode for Normal state + help: 0=manual, 1=anti-feed, 2=trade mode. + 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 62b9727b7..000000000 --- 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 000000000..51eb98792 --- /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 e3d65077f..000000000 --- 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 de33af612..000000000 --- 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 30c5bf147..000000000 --- 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 000000000..661ac9bd8 --- /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 000000000..105444b95 --- /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 000000000..7b831c396 --- /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 000000000..451b9df71 --- /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: Modbus Type + 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 f8d60b48a..000000000 --- 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 000000000..b150de856 --- /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 3e146f8e1..000000000 --- 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 000000000..df96a9b5b --- /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 # Watchdog, 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: Controllable battery component + help: + advanced: true + optional: true + - name: watchdog + example: + default: 60s + choice: [] + unit: + description: Watchdog + 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 643f372ad..000000000 --- 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 fc02fd8c4..000000000 --- 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 000000000..42d28e1c0 --- /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: Modbus Type + 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 000000000..8a83b9eeb --- /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: Modbus Type + 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 775ad5c2d..000000000 --- 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 000000000..734a4d8f7 --- /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 0d3c458f3..000000000 --- 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 000000000..d1c2ed781 --- /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: Modbus Type + 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 981283f06..000000000 --- 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 000000000..6f1583922 --- /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: Modbus Type + 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 e8ffec3dd..000000000 --- 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 000000000..6b5846524 --- /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, 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, 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: 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/powerfox-poweropti_0.yaml b/templates/release/en/meter/powerfox-poweropti_0.yaml deleted file mode 100644 index 414ced22d..000000000 --- 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 d92342d9e..000000000 --- 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 000000000..d31377a8b --- /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 000000000..e2a82f24d --- /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 # Third PV input, 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 # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, 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 # Third PV input, 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 # 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: | + 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 # Third PV input, 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 # 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: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: Third PV input + help: The inverter has a third PV input (MPPT3) + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Battery storage unit index + 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 000000000..3ba9c2ed5 --- /dev/null +++ b/templates/release/en/meter/rct-power.yaml @@ -0,0 +1,112 @@ +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 + cache: 30s # Cache, Time interval with when data should be reloaded from the vehicle (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 + 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) +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 28d75ab20..000000000 --- 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 000000000..efe18be51 --- /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: Modbus Type + 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 000000000..28103513e --- /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: Modbus Type + 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 000000000..e41247b89 --- /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: Modbus Type + 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 5c112c078..000000000 --- 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 000000000..668e920a5 --- /dev/null +++ b/templates/release/en/meter/saj-h2-series-hybrid-solar-inverter.yaml @@ -0,0 +1,207 @@ +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 + - 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 + - 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: Modbus Type + 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 870861690..000000000 --- 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 e8c51a742..000000000 --- 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 000000000..dcab8d1d6 --- /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: Modbus Type + 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 dcf6d62b7..000000000 --- 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 000000000..18e0962f0 --- /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: Modbus Type + 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 6b87e7b5f..000000000 --- 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 0932eb8d3..000000000 --- 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 000000000..bf12208f0 --- /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: Modbus Type + 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 c766da31f..000000000 --- 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 000000000..259ce5a1a --- /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 # Schema, [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: grid + host: 192.0.2.2 # IP address or hostname + 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 # Schema, [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: pv + host: 192.0.2.2 # IP address or hostname + 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 # Schema, [https, http] (optional) + advanced: | + type: template + template: senec-home + usage: battery + host: 192.0.2.2 # IP address or hostname + schema: https # Schema, [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: Schema + 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 faafe6214..000000000 --- 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 000000000..e4f7f023e --- /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: Modbus Type + 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 9a544572a..000000000 --- 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 1d9c00fb4..000000000 --- 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 000000000..beb9f06a7 --- /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 # Channel, 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 # Channel, 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 # Channel, 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: 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 new file mode 100644 index 000000000..a2e475473 --- /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 # Channel, 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 # Channel, 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 # Channel, 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: Channel + 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 1388f9196..000000000 --- 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 000000000..15b9de40f --- /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 7ee5fbfb3..000000000 --- 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 000000000..f7cd403f3 --- /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 # Channel, 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 # Channel, 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 # Channel, 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: 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 new file mode 100644 index 000000000..68caf993f --- /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 # Channel, 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 # Channel, 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 # Channel, 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: 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 new file mode 100644 index 000000000..b407be809 --- /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 # Channel, 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 # Channel, 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 # Channel, 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: 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 new file mode 100644 index 000000000..9728b0e1a --- /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 # Channel, 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 # Channel, 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 # Channel, 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: Channel + 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 000000000..21144ec53 --- /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 000000000..0b1753c2a --- /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 # Channel, 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 # Channel, 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 # Channel, 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: Channel + 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 f30ffb99e..000000000 --- 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 000000000..d72024581 --- /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 # Channel, 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 # Channel, 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 # Channel, 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: 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 new file mode 100644 index 000000000..16d64b0ef --- /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: Modbus Type + 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 938c0727f..000000000 --- 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 000000000..cf7a56906 --- /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: Modbus Type + 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 f5b3e946c..000000000 --- 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 000000000..973fde2e6 --- /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: Modbus Type + 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 f4a8b1239..000000000 --- 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 000000000..9d7669f6d --- /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 # ID, optional + advanced: | + type: template + template: sigenergy + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # ID, 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 # ID, optional + advanced: | + type: template + template: sigenergy + usage: pv + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # ID, 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 # ID, optional + advanced: | + type: template + template: sigenergy + usage: battery + host: 192.0.2.2 # IP address or hostname + port: 502 # Port, optional + id: 1 # ID, 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: ID + 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 5a38408be..000000000 --- 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 c92e82572..000000000 --- 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 f8fc9e139..000000000 --- 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 5464082c2..000000000 --- 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 905cf4247..000000000 --- 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 1fbd43906..000000000 --- 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 000000000..24f4f8205 --- /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: Modbus Type + 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 1f805c0ff..000000000 --- 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 000000000..d49180457 --- /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 f3aca2520..000000000 --- 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 2ed42b04b..000000000 --- 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 20a1d1218..000000000 --- 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 cda83af75..000000000 --- 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 000000000..8b8bb33c3 --- /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 332bf304a..000000000 --- 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 bfe5994b4..000000000 --- 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 746c98829..000000000 --- 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 18cda0ff7..000000000 --- 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 000000000..0bbcc8660 --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Watchdog + 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 000000000..3ee2397bc --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Watchdog + 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 000000000..19212b243 --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Watchdog + 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 000000000..fea114ced --- /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 000000000..6fe923551 --- /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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Watchdog + 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 000000000..92f9374c1 --- /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: Modbus Type + 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 2d6962964..000000000 --- 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 000000000..87f42dcfc --- /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: Modbus Type + 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 000000000..be4fbbd2e --- /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 95ab02e96..000000000 --- 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 000000000..28fec810b --- /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 000000000..75ba8eb90 --- /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 000000000..6b1c00a12 --- /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 000000000..e73f1656c --- /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 000000000..f3d6833e2 --- /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 000000000..b512e7a2e --- /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 000000000..651ceef58 --- /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 9786730bc..000000000 --- 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 59c03efc6..000000000 --- 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 332133f75..000000000 --- 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 135fe8a13..000000000 --- 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 43ae1f59d..000000000 --- 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 000000000..257cd0396 --- /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: Modbus Type + 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 000000000..b94da7c7f --- /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 # 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 + 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 # 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: | + 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 # 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: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 000000000..c84df68d6 --- /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 # 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 + 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 # 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: | + 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 # 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: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 000000000..24ca745a3 --- /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: Modbus Type + 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 000000000..2b6dcc015 --- /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 # 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 + 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 # 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: | + 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 # 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: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 000000000..c0a3e57ec --- /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 # 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 + 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 # 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: | + 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 # 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: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + 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 + 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 7b1bd8a22..000000000 --- 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 dee96b142..000000000 --- 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 000000000..be8201b90 --- /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 ff3f41dee..000000000 --- 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 000000000..0f9ba00cd --- /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 # Watchdog, 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 # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip', 'rs485'] + unit: + description: Modbus Type + 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: Watchdog + 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 ee5bada3a..000000000 --- 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 000000000..92439e1e4 --- /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: Modbus Type + 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 fee71b0b1..000000000 --- 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 000000000..74cd440bb --- /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 698d7af56..000000000 --- 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 e8f58cb7c..000000000 --- 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 000000000..846665c62 --- /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 # Watchdog, 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 # Watchdog, 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 # Watchdog, optional +params: + - name: modbus + example: + default: + choice: ['tcpip'] + unit: + description: Modbus Type + 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: Watchdog + 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 be7f036a9..000000000 --- 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 177b29e4e..000000000 --- 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 000000000..5c52c0f6b --- /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: Modbus Type + 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 000000000..1a453e4d2 --- /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: Modbus Type + 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 000000000..c149af876 --- /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 000000000..1ffad05d9 --- /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 2971f5426..000000000 --- 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 000000000..2b511aa61 --- /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 000000000..5bdc806f7 --- /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 66aeb6cf0..000000000 --- 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 000000000..12c6d813c --- /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 50634a9b3..000000000 --- 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 bf7afd541..000000000 --- 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 7d8650170..000000000 --- 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 000000000..a20c1b603 --- /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 000000000..a22cb55fd --- /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 # Third PV input, 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 # Third PV input, The inverter has a third PV input (MPPT3) (optional) + storageunit: 1 # Battery storage unit index, 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 # Third PV input, 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 # 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: | + 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 # Third PV input, 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 # 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: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: mppt3 + example: + default: false + choice: [] + unit: + description: Third PV input + help: The inverter has a third PV input (MPPT3) + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Battery storage unit index + 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 000000000..195c81bec --- /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 cc392d9a7..000000000 --- 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 b376dc5bd..000000000 --- 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 afa38d5a6..000000000 --- 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 000000000..48eb6ffa6 --- /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 # Delay, 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 # Delay, 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 # Delay, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Type + 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: Delay + 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 e698d3ec9..000000000 --- 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 94b6330bb..000000000 --- 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 c2dc05507..000000000 --- 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 060c4546d..000000000 --- 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 000000000..e8997210d --- /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 000000000..325a1185d --- /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 000000000..0dc8a04dc --- /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 000000000..1e7a3f38f --- /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 000000000..306952ced --- /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: # 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: # 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: Token + 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 a7b18d6e3..000000000 --- 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 191daa0c3..000000000 --- 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 000000000..db0124d33 --- /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 # Delay, 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 # Delay, 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 # Delay, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Type + 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: Delay + 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 000000000..7bed96e98 --- /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 6534c984f..000000000 --- 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 5e90620af..000000000 --- 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 3bc755a5b..000000000 --- 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 000000000..46978a33c --- /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: Modbus Type + 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 000000000..3a912101c --- /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: Modbus Type + 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 77e9733a0..000000000 --- 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 000000000..41096da82 --- /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: Modbus Type + 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 000000000..2560e56f8 --- /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: Modbus Type + 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 000000000..66f317f8e --- /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: Modbus Type + 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 86e1699f1..000000000 --- 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 a5f309d95..000000000 --- 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 000000000..10dcd6357 --- /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: Modbus Type + 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 10ff70493..000000000 --- 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 000000000..0794d3db4 --- /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: Modbus Type + 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 a37a482b6..000000000 --- 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 676b66949..000000000 --- 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 000000000..1c1ef1809 --- /dev/null +++ b/templates/release/en/meter/sunsynk-3p-hybrid-inverter.yaml @@ -0,0 +1,208 @@ +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 + - 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 + 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: Modbus Type + 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 000000000..7ca495d16 --- /dev/null +++ b/templates/release/en/meter/sunsynk-hp3-hybrid-inverter.yaml @@ -0,0 +1,232 @@ +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 # Battery storage unit index, 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 # 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 + 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 # 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) + includegenport: # Treat GEN port as solar input, optional +params: + - name: modbus + example: + default: + choice: ['rs485', 'tcpip'] + unit: + description: Modbus Type + help: + advanced: false + optional: true + - name: storageunit + example: + default: 1 + choice: [] + unit: + description: Battery storage unit index + 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 000000000..05c3bd6fd --- /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: Modbus Type + 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 000000000..4ac1e2a40 --- /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: Modbus Type + 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 000000000..7ab4c4858 --- /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: Modbus Type + 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 000000000..fa3de4ae9 --- /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 # Delay, 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 # Delay, 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 # Delay, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Type + 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: Delay + 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 8aa3aa63f..000000000 --- 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 ff3d6e34e..000000000 --- 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 000000000..15175bbf0 --- /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 8f0b4b061..000000000 --- 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 000000000..9a93f1c7f --- /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 000000000..4edf7dc33 --- /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 ffc7aa02d..000000000 --- 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 000000000..469a327dd --- /dev/null +++ b/templates/release/en/meter/tesla-powerwall.yaml @@ -0,0 +1,123 @@ +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: # 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: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (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: # 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: # Refresh token, optional + siteId: # Site ID, optional product identifier of the energy site, use to override autodectction (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: # 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: # 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: + - 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: Refresh token + help: + advanced: false + optional: true + - name: siteId + example: + default: + choice: [] + unit: + description: Site ID + 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 c2595a9d0..000000000 --- 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 8c2453302..000000000 --- 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 000000000..ef324fdd3 --- /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 # Token + homeid: 96a14971-525a-4420-aae9-e5aedaa129ff # Home ID, optional +params: + - name: token + example: 5K4MVS-OjfWhK_4yrjOlFe1F6kJXPVf7eQYggo8ebAE + default: + choice: [] + unit: + description: Token + help: + advanced: false + optional: false + - name: homeid + example: 96a14971-525a-4420-aae9-e5aedaa129ff + default: + choice: [] + unit: + description: Home ID + 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 6da33b3f3..000000000 --- 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 000000000..82419a06a --- /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 000000000..aec8e0d43 --- /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 b20e61dbe..000000000 --- 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 b6a2d77db..000000000 --- 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 8ab8314c6..000000000 --- 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 000000000..a30afc18f --- /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 000000000..2ecbbcba3 --- /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 000000000..eac635c83 --- /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 000000000..178208705 --- /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 000000000..32111518e --- /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 2b1fffb1b..000000000 --- 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 000000000..53e03f6e5 --- /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: Modbus Type + 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 000000000..54fe30cef --- /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: Modbus Type + 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 000000000..c7202109b --- /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: Modbus Type + 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 000000000..27dc15404 --- /dev/null +++ b/templates/release/en/meter/victron-energy.yaml @@ -0,0 +1,118 @@ +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) + - 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 + - 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: Grid meter VRM instance + help: 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 c505657b1..000000000 --- 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 000000000..775147ce4 --- /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: Modbus Type + 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 629855051..000000000 --- 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 afd01bc3a..000000000 --- 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 01609205c..000000000 --- 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 000000000..442889e92 --- /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: http://zaehler.network.local:8080/api/data # Middleware URL, optional + importuuid: # Import UUID + exportuuid: # Export UUID +params: + - name: url + example: http://zaehler.network.local:8080/api/data + default: + choice: [] + unit: + description: Middleware URL + help: + advanced: false + optional: true + - name: importuuid + example: + default: + choice: [] + unit: + description: Import UUID + help: + advanced: false + optional: false + - name: exportuuid + example: + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..b477cc1a5 --- /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: http://zaehler.network.local:8080/api/data # Middleware URL, optional + uuid: # UUID +params: + - name: url + example: http://zaehler.network.local:8080/api/data + default: + choice: [] + unit: + description: Middleware URL + help: + advanced: false + optional: true + - name: uuid + example: + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..85053d4b0 --- /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: # 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: 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 new file mode 100644 index 000000000..dcd661aff --- /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: # UUID + advanced: | + type: template + template: vzlogger + usage: grid + host: 192.0.2.2 # IP address or hostname + port: 8081 # Port, optional + uuid: # UUID + scale: 1 # Scale factor, Multiply by this value (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 + 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: UUID + 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: 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + example: + default: + choice: [] + unit: + 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 + 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 647ea0d5d..000000000 --- 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 000000000..31c613759 --- /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: Modbus Type + 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 4b3f34dd3..000000000 --- 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 000000000..7d4239f1d --- /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 # Delay, 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 # Delay, 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 # Delay, optional +params: + - name: modbus + example: + default: + choice: ['rs485'] + unit: + description: Modbus Type + 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: Delay + 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 ce4ad627a..000000000 --- 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 eab7143b0..000000000 --- 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 9c26d1667..000000000 --- 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 ee4278c70..000000000 --- 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 44bd73bc2..000000000 --- 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 000000000..5eccef801 --- /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: Modbus Type + 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 000000000..54e881fb9 --- /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: Modbus Type + 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 000000000..f90c99712 --- /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: Modbus Type + 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 000000000..ad100e329 --- /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: Modbus Type + 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 000000000..bca068a50 --- /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 3d4b310f3..000000000 --- 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 000000000..ce0286b0f --- /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: Modbus Type + 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 000000000..c382b4a2e --- /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: Modbus Type + 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 000000000..1acf6753d --- /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 # 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 # 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 # 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 # 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: + - name: account + example: dev@zendure.com + default: + choice: [] + unit: + description: Account ID + help: + advanced: false + optional: false + - name: serial + example: VU5D99F74021B04 + default: + choice: [] + unit: + description: Serial + 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: Region + 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 a0dec95e1..000000000 --- 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 000000000..c16e4c51d --- /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 000000000..69caa5297 --- /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 000000000..16fa4bf45 --- /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 000000000..c30fd68c8 --- /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: # Token, optional + siteid: # Site ID, optional + channel: # Channel, optional + advanced: | + type: template + template: amber + 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) +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + help: + advanced: false + optional: true + - name: siteid + example: + default: + choice: [] + unit: + description: Site ID + help: + advanced: false + optional: true + - name: channel + example: + default: + choice: [] + unit: + description: Channel + 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 75fc5db1e..000000000 --- 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 000000000..40bc60a97 --- /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 # Region, [DE, AT] + advanced: | + type: template + template: awattar + 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) +params: + - name: region + example: AT + default: + choice: ['DE', 'AT'] + unit: + description: Region + 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 13219b380..000000000 --- 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 000000000..dffcd0ff3 --- /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: # Token + zone: DE # Zone, 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: Token + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..7738d1928 --- /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: # Token + zone: DE # Zone, see https://api.electricitymap.org/v3/zones +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + help: + advanced: false + optional: false + - name: zone + example: DE + default: + choice: [] + unit: + 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/electricitymaps-free_0.yaml b/templates/release/en/tariff/electricitymaps-free_0.yaml deleted file mode 100644 index 272405316..000000000 --- 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 141d236a5..000000000 --- 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 000000000..9961d6bf8 --- /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 # Region, [dk1, dk2] + advanced: | + type: template + template: energinet + 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) +params: + - name: region + example: dk1 + default: + choice: ['dk1', 'dk2'] + unit: + description: Region + 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 2a27ee410..000000000 --- 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 f846ebb79..000000000 --- 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 000000000..04ee26c10 --- /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: # 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: # 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 # Interval, optional +params: + - name: token + example: + default: + choice: [] + unit: + description: Token + 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: Provider + 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: Interval + 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 494b84df7..000000000 --- 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 000000000..7b34aa46a --- /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: # 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: # 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) +params: + - name: securitytoken + example: + default: + choice: [] + unit: + 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 + - name: domain + example: BZN|DE-LU + default: + choice: [] + unit: + description: Domain + 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 c050019d0..000000000 --- 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 000000000..16fb101e9 --- /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 # Interval, 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: Interval + 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 9a9f7e856..000000000 --- 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 000000000..213272af3 --- /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 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 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) +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: Bidding zone + help: see 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 000000000..03111e941 --- /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 f36277e03..000000000 --- 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 000000000..ac7ea7b10 --- /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 56bc8fd34..000000000 --- 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 000000000..e4e4dc9a9 --- /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: # ZIP code + token: # Token, Token for accessing the API from https://console.corrently.io (optional) +params: + - name: zip + example: + default: + choice: [] + unit: + description: ZIP code + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + 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/gr\303\274nstromindex_0.yaml" "b/templates/release/en/tariff/gr\303\274nstromindex_0.yaml" deleted file mode 100644 index 05b927e46..000000000 --- "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 000000000..fc7c387d1 --- /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 # 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: Region + 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: 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/ngeso_0.yaml b/templates/release/en/tariff/ngeso_0.yaml deleted file mode 100644 index ce118924a..000000000 --- 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 000000000..220a55685 --- /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 # 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 # 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) +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: Region + help: + advanced: false + optional: true + - name: currency + example: + default: EUR + choice: ['DKK', 'EUR', 'NOK', 'PLN', 'RON', 'SEK'] + unit: + description: Currency + 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 0196acdc2..000000000 --- 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 84078e9cb..000000000 --- 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 000000000..e7e5f3cf8 --- /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: # API Key + accountNumber: X-XXXXXXXX # Account Number, Only required if you have multiple accounts. (optional) +params: + - name: apiKey + example: + default: + choice: [] + unit: + description: API Key + help: + advanced: false + optional: false + - name: accountNumber + example: X-XXXXXXXX + default: + choice: [] + unit: + 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 new file mode 100644 index 000000000..b71886e83 --- /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 # 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: Product Code + 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: Region + 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: 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/octopus-productcode_0.yaml b/templates/release/en/tariff/octopus-productcode_0.yaml deleted file mode 100644 index 2e8bd67f9..000000000 --- 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 000000000..673db71d1 --- /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 # Interval, 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: Interval + 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 34129af03..000000000 --- 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 000000000..0c9d4e720 --- /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 # 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: Client ID + help: + advanced: false + optional: false + - name: clientsecret + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4a + default: + choice: [] + unit: + description: Client Secret + help: + advanced: false + optional: false + - name: contract + example: 100523456 + default: + choice: [] + unit: + 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/ostrom_0.yaml b/templates/release/en/tariff/ostrom_0.yaml deleted file mode 100644 index c7750b8eb..000000000 --- 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 000000000..3f0377197 --- /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 88607b684..000000000 --- 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 000000000..f6c6bd8b9 --- /dev/null +++ b/templates/release/en/tariff/smartenergy-smartcontrol.yaml @@ -0,0 +1,46 @@ +template: smartenergy +product: + identifier: smartenergy-smartcontrol + brand: SmartEnergy + description: smartCONTROL + group: Dynamic electricity price +countries: ["AT"] +requirements: ["skiptest"] +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 2ebaa0c84..000000000 --- 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 000000000..cb0f46106 --- /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: # API Token + advanced: | + type: template + template: solcast + 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: Ressource ID of your site + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: API Token + help: + advanced: false + optional: false + - name: from + example: + default: + choice: [] + unit: + description: Start time + help: Start time of data retrieval, specified in full hours, e.g. "6" + advanced: true + optional: true + - name: to + example: + default: + choice: [] + unit: + description: End time + 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: Interval + 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 3ca5b561e..000000000 --- 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 000000000..4b5937ba9 --- /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 # 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 # 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) +params: + - name: contractid + example: ffffffff-4444-6666-2222-aaaaaabbbbbb + default: + choice: [] + unit: + description: Contract ID + 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: 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 + - 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 b2a630fee..000000000 --- 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 000000000..13961ca5b --- /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 # 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 # 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) +params: + - name: token + example: 476c477d8a039529478ebd690d35ddd80e3308ffc49b59c65b142321aee963a4 + default: + choice: [] + unit: + description: API Token + help: + advanced: false + optional: false + - name: homeid + example: cc83e83e-8cbf-4595-9bf7-c3cf192f7d9c + default: + choice: [] + unit: + description: Home ID + 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 218af3caa..000000000 --- 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 000000000..91a7b532d --- /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 # Interval, 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: Interval + 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 c53a8a999..000000000 --- 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 000000000..5145bed7f --- /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, 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) + 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 + 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 + 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 41b779693..000000000 --- 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 000000000..bfba6a04d --- /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, 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) + 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 + 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 + 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 b160ad886..000000000 --- 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 000000000..2c93a90c3 --- /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: # Captcha Token + 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: # 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, 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) + 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: Captcha 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 + 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 + 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 893d766bf..000000000 --- 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 a6431a96d..000000000 --- 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 000000000..7291cb42a --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 80a90a75a..000000000 --- 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 c964a5aa9..000000000 --- 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 000000000..554a1386b --- /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, 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) + 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 + 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 + 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 15a799dd5..000000000 --- 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 000000000..fc5f7c379 --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 dbdac3414..000000000 --- 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 1f6c4b717..000000000 --- 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 000000000..820c3ae80 --- /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: # 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: # 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, 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) +params: + - name: akey + example: + default: + choice: [] + unit: + description: API Key + help: + advanced: false + optional: false + - name: token + example: + default: + choice: [] + unit: + description: Token + 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 + 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 + 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 25089ee73..000000000 --- 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 000000000..921bfcde4 --- /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: # 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: # 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, 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) + 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: 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 + - 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 + 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 + 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 4cf94368d..000000000 --- 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 599820a9d..000000000 --- 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 d3298dedd..000000000 --- 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 d4aa6aec9..000000000 --- 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 000000000..d3be29013 --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 000000000..bf74ba3d1 --- /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, 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) +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 + 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 + 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 000000000..fa205c133 --- /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, 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) + 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 + 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 + 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 7ca677a2e..000000000 --- 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 9d34e5bee..000000000 --- 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 000000000..b4b4994f2 --- /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, 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, 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, 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) + 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 + help: including ioBroker.simple-api Port + 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 + 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 + 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 000000000..ecc5abc9a --- /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, 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) +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 + 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 + 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 f818e4ff4..000000000 --- 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 000000000..272fab74f --- /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: # 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: # 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, 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) + 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: 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 + - 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 + 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 + 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 000000000..46a33ae75 --- /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, 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) + 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 + 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 + 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 377fd3476..000000000 --- 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 000000000..c3b557fb7 --- /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 # 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 + 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 # 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, 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) + 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: Region + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 907cd189d..000000000 --- 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 000000000..ddd6acf4e --- /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, 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) + 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 + 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 + 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 000000000..af8f0fa80 --- /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, 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) +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 + 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 + 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 50a0ee682..000000000 --- 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 7f155403e..000000000 --- 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 000000000..2d01ab6ff --- /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: # Captcha Token + 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: # 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, 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) + 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: Captcha 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 + 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 + 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 a70fdf8cd..000000000 --- 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 000000000..c9adbf935 --- /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, 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) + 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 + 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 + 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 98cb225ed..000000000 --- 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 000000000..24f45cbc9 --- /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, 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) + 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 + 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 + 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 88da497a9..000000000 --- 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 000000000..83518cecc --- /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, 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) + 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 + 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 + 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 000000000..e305ff7f9 --- /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, 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) + 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 + 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 + 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 2e3121a59..000000000 --- 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 000000000..086dd8908 --- /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 7c39fa567..000000000 --- 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 f9be0e2b9..000000000 --- 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 000000000..f6ec11d4f --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 c85598d2f..000000000 --- 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 000000000..002ae0cac --- /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: # Vehicle ID + 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: # 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, 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 + 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: Vehicle ID + 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 + 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 + 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: Server + 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 f1b2c938f..000000000 --- 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 000000000..99222be8a --- /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: # Access token + refreshToken: # Refresh token + 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: # 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, 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) + 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: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 b5c713d65..000000000 --- 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 000000000..b05f19a3d --- /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, 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) + 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 + 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 + 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 9b9422c13..000000000 --- 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 000000000..51c85ece1 --- /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 # 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 + 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, 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, Can lead to increased discharge of the 12V battery. (optional) +params: + - name: url + example: http://192.0.2.2 + default: + choice: [] + unit: + description: URL + 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 + 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 + 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: 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 new file mode 100644 index 000000000..7908ecd9d --- /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, 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) + 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 + 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 + 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 514bbde56..000000000 --- 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 000000000..e3ca4aca6 --- /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, 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) + 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 + 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 + 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 000000000..928db2d78 --- /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, 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) + 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 + 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 + 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 396e5f01c..000000000 --- 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 000000000..121e0beac --- /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, 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) + 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 + 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 + 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 000000000..e5f20a635 --- /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, 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) + 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 + 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 + 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 000000000..4bad511b9 --- /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 # 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 + 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 # 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, 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) + 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: Region + help: + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: Access token + help: + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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 a8b2821f5..000000000 --- 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 235fd7691..000000000 --- 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 000000000..94ada0edf --- /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, 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, 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, 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) +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: URL + 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 + 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 + 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 735508690..000000000 --- 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 000000000..444740c9f --- /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, 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, 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, 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 # 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 + 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: Client ID + help: from [Tesla Developer App](https://developer.tesla.com/dashboard). + advanced: false + optional: false + - name: accessToken + example: + default: + choice: [] + unit: + description: Access token + help: from [myteslamate.com](https://app.myteslamate.com/). + advanced: false + optional: false + - name: refreshToken + example: + default: + choice: [] + unit: + description: Refresh token + 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 + 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 + 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: 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 + - name: proxyToken + example: + default: + choice: [] + unit: + 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 + - 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 24e6b4cf3..000000000 --- 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 000000000..06d1c2df6 --- /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 # URL + 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 # 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, 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) +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: URL + 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 + 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 + 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 73c9e7859..000000000 --- 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 000000000..1e05c0aad --- /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, 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) +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 + 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 + 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 1d9f0a6a8..000000000 --- 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 000000000..9f5633f57 --- /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, 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) +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 + 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 + 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 77bf181aa..000000000 --- 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 000000000..96ee894eb --- /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, 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) + 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 + 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 + 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 072dfea03..000000000 --- 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 000000000..0afcbc6c8 --- /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, 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) + 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 + 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 + 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 36a856550..000000000 --- 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 000000000..44f00466b --- /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, 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) + 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 + 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 + 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 3ecde57c1..000000000 --- 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 000000000..462c33905 --- /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, 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, 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, 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) +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: VCC API Key + help: from [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientId + example: + default: + choice: [] + unit: + description: Client ID + help: from [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: clientSecret + example: + default: + choice: [] + unit: + description: Client Secret + help: from [Volvo Developer App](https://developer.volvocars.com/). + advanced: false + optional: false + - name: redirectUri + example: + default: + choice: [] + unit: + 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 + 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 + 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 + 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 000000000..d5176ea38 --- /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, 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) +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 + 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 + 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 ccb0e75b8..000000000 --- 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 99fe3110e..000000000 --- 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 000000000..88939083c --- /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, 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) + 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 + 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 + 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 79052fe3a..000000000 --- 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) diff --git a/tsconfig.json b/tsconfig.json new file mode 100644 index 000000000..a80f247a1 --- /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"] +}