Gompman
(Gompman)
December 14, 2021, 8:58am
1
I am currently trying to connect my Wallbox Warp2 to HA via mqtt. here I come across the following problem which I can’t get cleared from the documentation.
The aim should be to set up an mqqt number in the Configuration.yaml via which the max. Charging current can be set.
By sending the message {“current”: 8000} to the topic warp/ABC/evse/current_limit , the charging current can be limited to 8 amps
The answer is given by: warp/ABC/evse/max_charging_current {“max_current_configured”: 8000, “max_current_incoming_cable”: 13000, “max_current_outgoing_cable”: 16000}
where “max_current_configured” is interesting here.
1. question:
How do I set up the configuration in yaml?
2. question:
As soon as I set limits for the value (6000 -32000)
The operation via Lovelace is almost impossible.
E.g. 6000 is in the field. I want to change to 6500 (I have to remove a zero to replace it with a five) this does not work and the display jumps back to 6000?!?!?!
Setting values between 6000 and 32000 is actually not possible via the user interface.
Here´s my code:
number:
- platform: mqtt
name: "Wallbox max Ladestrom"
unique_id: 52cc64f8-8f77-486b-abe7-124431eeb983
command_topic: "warp2/garage/evse/current_limit"
state_topic: "warp2/garage/evse/max_charging_current"
#command_template: '{{"current": value}}'
value_template: '{{value_json.current}}'
unit_of_measurement: "mA"
min: 6000
max: 32000
step: 10
Lars72
(Lars Künnemann)
March 9, 2022, 1:53pm
2
Hi,
did you manage to integrate the Warp2 wallbox?
I would be interested, since I plan to do the same.
Regards
Lars
1 Like
Gompman
(Gompman)
April 11, 2022, 12:07pm
3
integration worked but Tinkerforge published the new 2.xx Firmware with api changes.
bbr111
(Benjamin)
April 21, 2022, 9:03pm
4
Here some snips from my config.
Warp2 Pro Charger with Firmware V2.0.1
binary_sensor:
- platform: mqtt
name: "Wallbox Ladekabel verbunden"
state_topic: "warp2/WDB/evse/state"
device_class: plug
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.charger_state in [1, 2, 3] }}'
payload_on: 'True'
payload_off: 'False'
- platform: mqtt
name: "Wallbox Fehler"
state_topic: "warp2/WDB/evse/state"
device_class: problem
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.charger_state in [4] }}'
payload_on: 'True'
payload_off: 'False'
- platform: mqtt
name: "Wallbox verfügbar"
state_topic: "warp2/WDB/evse/low_level_state"
device_class: connectivity
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.uptime > 0 }}'
expire_after: 30
payload_on: 'True'
payload_off: 'False'
- platform: mqtt
name: "Wallbox Ladevorgang"
state_topic: "warp2/WDB/evse/state"
device_class: battery_charging
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.charger_state in [3] }}'
payload_on: 'True'
payload_off: 'False'
- platform: mqtt
name: "Wallbox Extern aktiviert"
state_topic: "warp2/WDB/evse/external_enabled"
json_attributes_template: '{{ value_json }}'
value_template: "{{ value_json.enabled }}"
payload_on: True
payload_off: False
- platform: mqtt
name: "Wallbox Benutzer aktiviert"
state_topic: "warp2/WDB/evse/user_enabled"
json_attributes_template: '{{ value_json }}'
value_template: "{{ value_json.enabled }}"
payload_on: True
payload_off: False
sensor:
- platform: mqtt
name: "Wallbox Leistung"
state_topic: "warp2/WDB/meter/values"
value_template: "{{ value_json.power }}"
device_class: power
unit_of_measurement: "W"
- platform: mqtt
name: "Wallbox Zählerstand"
state_topic: "warp2/WDB/meter/values"
value_template: "{{ value_json.energy_abs }}"
device_class: energy
unit_of_measurement: "kWh"
- platform: mqtt
name: "Wallbox Externe Freigabe"
state_topic: "warp2/WDB/evse/external_current"
value_template: "{{ value_json.current}}"
- platform: mqtt
name: "Wallbox Benutzer Freigabe"
state_topic: "warp2/WDB/evse/user_current"
value_template: "{{ value_json.current}}"
switch:
- platform: mqtt
name: "Wallbox Maximaler Ladestrom"
command_topic: "warp2/WDB/evse/current_limit"
payload_on: '{"current": 16000}'
payload_off: '{"current": 6000}'
state_topic: "warp2/WDB/evse/max_charging_current"
value_template: '{{ value_json.max_current_configured >= 16000 }}'
state_on: "True"
state_off: "False"
json_attributes_template: "{{ value_json }}"
- platform: mqtt
name: "Wallbox Automatisches Laden"
icon: mdi:ev-plug-type2
command_topic: "warp2/WDB/evse/auto_start_charging_update"
payload_on: '{"auto_start_charging": true}'
payload_off: '{"auto_start_charging": false}'
state_topic: "warp2/WDB/evse/auto_start_charging"
value_template: '{{ value_json.auto_start_charging }}'
state_on: "True"
state_off: "False"
- platform: mqtt
name: "Wallbox Ladevorgang"
icon: mdi:battery-charging
command_topic: "warp2/WDB/evse/charging_command"
state_topic: "warp2/WDB/evse/state"
value_template: '{{ value_json.vehicle_state in [2] }}'
state_on: "True"
state_off: "False"
- platform: template
switches:
wallbox_ladevorgang:
friendly_name: "Wallbox Ladevorgang"
icon_template: mdi:battery-charging
value_template: '{{ is_state("binary_sensor.wallbox_ladevorgang", "on") }}'
turn_on:
service: mqtt.publish
data:
topic: warp2/WDB/evse/start_charging
payload: 'null'
turn_off:
service: mqtt.publish
data:
topic: warp2/WDB/evse/stop_charging
payload: 'null'
1 Like
hathon
January 15, 2023, 11:13pm
5
i got the message that ii have to rearrange the config based on MQTT Sensor - Home Assistant
But now I’m faced that the - platform: template is not allowed anymore.
@bbr111 : do you have a config example for the actual HA version ?
bbr111
(Benjamin)
January 16, 2023, 5:28am
6
mqtt:
binary_sensor:
- name: "Wallbox Ladekabel verbunden"
state_topic: "warp2/WDB/evse/state"
device_class: plug
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.charger_state in [1, 2, 3] }}'
payload_on: 'True'
payload_off: 'False'
- name: "Wallbox Fehler"
state_topic: "warp2/WDB/evse/state"
device_class: problem
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.charger_state in [4] }}'
payload_on: 'True'
payload_off: 'False'
- name: "Wallbox verfügbar"
state_topic: "warp2/WDB/evse/low_level_state"
device_class: connectivity
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.uptime > 0 }}'
expire_after: 30
payload_on: 'True'
payload_off: 'False'
- name: "Wallbox Ladevorgang"
state_topic: "warp2/WDB/evse/state"
device_class: battery_charging
json_attributes_template: '{{ value_json }}'
value_template: '{{ value_json.charger_state in [3] }}'
payload_on: 'True'
payload_off: 'False'
- name: "Wallbox Extern aktiviert"
state_topic: "warp2/WDB/evse/external_enabled"
json_attributes_template: '{{ value_json }}'
value_template: "{{ value_json.enabled }}"
payload_on: True
payload_off: False
- name: "Wallbox Benutzer aktiviert"
state_topic: "warp2/WDB/evse/user_enabled"
json_attributes_template: '{{ value_json }}'
value_template: "{{ value_json.enabled }}"
payload_on: True
payload_off: False
switch:
- command_topic: "warp2/WDB/evse/current_limit"
name: "Wallbox Maximaler Ladestrom"
payload_on: '{"current": 16000}'
payload_off: '{"current": 6000}'
state_topic: "warp2/WDB/evse/max_charging_current"
value_template: '{{ value_json.max_current_configured >= 16000 }}'
state_on: "True"
state_off: "False"
json_attributes_template: "{{ value_json }}"
- command_topic: "warp2/WDB/evse/auto_start_charging_update"
name: "Wallbox Automatisches Laden"
icon: mdi:ev-plug-type2
payload_on: '{"auto_start_charging": true}'
payload_off: '{"auto_start_charging": false}'
state_topic: "warp2/WDB/evse/auto_start_charging"
value_template: '{{ value_json.auto_start_charging }}'
state_on: "True"
state_off: "False"
- command_topic: "warp2/WDB/evse/charging_command"
name: "Wallbox Ladevorgang"
icon: mdi:battery-charging
state_topic: "warp2/WDB/evse/state"
value_template: '{{ value_json.vehicle_state in [2] }}'
state_on: "True"
state_off: "False"
sensor:
- name: "Wallbox Leistung"
state_topic: "warp2/WDB/meter/values"
value_template: "{{ value_json.power }}"
device_class: power
unit_of_measurement: "W"
- name: "Wallbox Zählerstand"
state_topic: "warp2/WDB/meter/values"
value_template: "{{ value_json.energy_abs }}"
device_class: energy
unit_of_measurement: "kWh"
- name: "Wallbox Externe Freigabe"
state_topic: "warp2/WDB/evse/external_current"
value_template: "{{ value_json.current}}"
- name: "Wallbox Benutzer Freigabe"
state_topic: "warp2/WDB/evse/user_current"
value_template: "{{ value_json.current}}"
- name: "Wallbox Current Charge Time"
state_topic: "warp2/WDB/charge_tracker/current_charge"
value_template: "{{ value_json.timestamp_minutes}}"
switch:
- platform: template
switches:
wallbox_ladevorgang:
friendly_name: "Wallbox Ladevorgang"
icon_template: mdi:battery-charging
value_template: '{{ is_state("binary_sensor.wallbox_ladevorgang", "on") }}'
turn_on:
service: mqtt.publish
data:
topic: warp2/WDB/evse/start_charging
payload: 'null'
turn_off:
service: mqtt.publish
data:
topic: warp2/WDB/evse/stop_charging
payload: 'null'
Es müsste laut WARP2 Firmware jetzt auch eine AutoDiscovery geben. oder die müsste bald kommen.
opened 11:30AM - 27 Apr 22 UTC
closed 03:23PM - 22 Nov 22 UTC
enhancement
https://www.tinkerunity.org/topic/6431-warp-in-home-assistant-via-mqtt-und-http-… api/#comment-41189
Seems to be supported in Home Assistant, openHAB and Domoticz. Implementing the auto discovery topics could be an easy way to add support for those systems. This would also make sure that the "bindings" match to the available API, as they are contained in the firmware itself.