Add support for Wpl13 #70
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kr0ner
added
enhancement
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
|
I get an error when compiling... And this is my yaml: esphome:
name: esp32-heatingpump
friendly_name: ESP32-C6-Zero for Stiebel Eltron WPE-I 08 HK 230 Premium
platformio_options:
build_flags:
- "-std=gnu++17"
build_unflags:
- "-std=gnu++11"
- "-fno-rtti"
esp32:
board: esp32-c6-devkitc-1
variant: esp32c6
framework:
#type: arduino
type: esp-idf
version: "5.3.1"
platform_version: 6.9.0
# Enable logging
logger:
level: INFO
baud_rate: 0
hardware_uart: UART1
# Enable Home Assistant API
api:
encryption:
key: "--REDACTED--"
ota:
- platform: esphome
password: "--REDACTED--"
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
use_address: 10.0.110.31
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "Heatingpump Fallback Hotspot"
password: "--REDACTED--"
time:
- platform: homeassistant
id: homeassistant_time
substitutions:
interval_very_fast: 15s
interval_fast: 30s
interval_medium: 60s
interval_slow: 5min
interval_very_slow: 15min
interval_once_in_a_while: 1h
entity_room_temperature: "sensor.durchschnittstemperatur_haus_ohne_keller"
entity_humidity: "sensor.durchschnitt_luftfeuchtigkeit_haus"
#########################################
# #
# SPI configuration #
# #
#########################################
#spi:
# id: McpSpi
# clk_pin: GPIO14
# mosi_pin: GPIO13
# miso_pin: GPIO4
#########################################
# #
# CAN configuration #
# #
#########################################
canbus:
- id: !extend wp_can
# platform: mcp2515
# spi_id: McpSpi
# cs_pin: GPIO15
platform: esp32_can
tx_pin: GPIO16
rx_pin: GPIO15
can_id: 0x680
use_extended_id: false
bit_rate: 20kbps
#########################################
# #
# Buttons #
# #
#########################################
#button:
# - platform: restart
# name: "Restart ESP32-PoE Technik"
#########################################
# #
# Ethernet Konfiguration #
# #
#########################################
#ethernet:
# type: LAN8720
# mdc_pin: GPIO23
# mdio_pin: GPIO18
# clk_mode: GPIO0_OUT
# phy_addr: 0
# power_pin: GPIO12
#########################################
# #
# Packages #
# #
#########################################
packages:
# energymeter: !include OneESP32ToRuleThemAll/yaml/energymeter.yaml
# watermeter: !include OneESP32ToRuleThemAll/yaml/watermeter.yaml
# sensors: !include OneESP32ToRuleThemAll/yaml/sensors.yaml
# thz404: !include OneESP32ToRuleThemAll/yaml/thz404.yaml
# thz504: !include OneESP32ToRuleThemAll/yaml/thz504.yaml
# thz55eco: !include OneESP32ToRuleThemAll/yaml/thz5_5_eco.yaml
# ttf07: !include OneESP32ToRuleThemAll/yaml/ttf07.yaml
wpl13: !include OneESP32ToRuleThemAll/yaml/wpl13.yaml
# kondensatpumpe: !include OneESP32ToRuleThemAll/yaml/kondensatpumpe.yaml
#########################################
# #
# EVU Sperre #
# #
#########################################
#switch:
# - platform: gpio
# name: "EVU Sperre"
# id: evu_sperre
# pin: GPIO5
switch:
# Restart ESP device
- platform: restart
name: "Boiler room ESP restart"
id: restart_esp_heatpump
# local led light
- platform: gpio
id: onboard_led
pin:
number: GPIO2
mode: OUTPUT
restore_mode: ALWAYS_OFF
|
|
There was a header missing. Should build now |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
|
Yes, it builds now... and I was able to run it, but... it seems I don't get any messages anymore as soon as it sends the first messages like 0x6a2... Is there an easy way to not send any messages and just listening for messages? Sorry, but I'm not a C++ dev.... |
|
https://github.com/kr0ner/OneESP32ToRuleThemAll/blob/master/yaml/common.yaml#L60 |
|
yes, just found it ;-) now I get a lot of messages: |
|
You got a weird mixture of my code on the other there ... e.g. HILFSKESSELSOLL is nowhere defined in my code, but still edit: I saw that this one is already correctly mapped ... so maybe continue with stuff like VORLAUFIST, VORLAUFSOLL and so on. Keep me in the loop so that we can progress faster ;) |
|
fyi: I added HILFSKESSELSOLL myself, since this was already catched with the other repo's code... I just need to verify if it's really that value... |
|
ok, no problemo ... everything is fine then :) was just wondering where this thingy comes from and locally it only found one reference in the trash of the old repo :D |
|
I think I'm too stupid... on top of that, I have no idea whether what I've tried is right... 
|
No, you are not. There are multiple sources for each property. The one with zero is the one that request the value, important so that we can later fake that request to get the updated value on demand. And the other two make me think that HK1 and HK2 are actually 0x480 and 0x339 😉 For the screenshots: trust me, we are almost there 👍 |
|
I'll now try to create some pictures of the screens and also attach a bigger log or that time range... |
|
@adrai based on what I could guess from the logs I updated the yaml and simplified it a bit for now. Also added some hints there to guide you ... first thing we need to do now is to identify the can members correctly ... once we have that we should find out how to request stuff and after that it is your turn to fill the list of properties ;) |
|
Btw. do you have more than one ESP connected to the heatpump? Cause the amount of CAN messages is quite high ... or are you scrolling through the menu while logging? |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
|
No, I have just 1 ESP. Yes, while logging I made those screen pictures... but I did not modify any setting. Will check your update tomorrow if I have enough time. |
|
wanted to test it one time before going to sleep ;-) and also |
|
@adrai can you please enable verbose logging? I need to see those lines as well
So that just means we are registering the callback for the wrong CAN-Id. That is just a config issue and it will get better soon. The initial setup is always a bumpy road. I changed the ids again and added an additional log.
So whenever the view in the display changes and values are being displayed, there were CAN messages sent out ;) The heatpump sends most sensor values only on request, which is a CAN message either sent by us or by the display. |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
|
logs_esp32-heatingpump_logs.txt |
|
1, no longer ignoring write commands |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
|
I think I found other values: I have a new set of logs and pics: 
Some questions: |
|
btw. just dropping here a larger log file from the last half an hour... 
|
Because the response to our request is 32768 🤷 How can you obtain the RAUMISTTEMP_HK1 manually? |
I have no clue. There is also 0x514 |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
I'd say we focus now on getting the system stable and to a point where we can merge the first version to master. 1, Can you please click through "Programmschalter" and find the ID that keeps changing when you select "Automatik", "Warmwasser", "Handbetrieb" and so on. Please focus on the important values first. e.g. hot water temp ist/soll , rücklauftemp, raumeinfluss, heizleistung, heizkreispumpe leistung, hysterese warmwasser, and leistungsaufnahme + wärmemenge for COP calculation. After we got those, i'll get the stuff into shape and merge it. Next step is to enable Programmschalter and the climate controls for heating and hot water. After that COP calculation |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
There is just the FET2 attached to the bus (outside of the heatpump)... I use the heatpump only for heating, not for warm water.
I have these options: I changed the status manually and traced the logs, but I have no clue.... |
|
so looks like 0x480 is the FES then
thanks, gonna have a look later |
looks like the mapping of the TTF07c. https://github.com/mkaiser/OneESP32ToRuleThemAll/blob/edf095dfec1b9aaff635bd644db8eb59c3f2f504/yaml/ttf07.yaml#L398 Betriebszustand here: |
|
@mkaiser I think that the TTF uses different encoding ... it uses the bits while WPL13 uses numbers 0 to 5 |
|
The GitHub Actions build has failed. Check the workflow run details for more information. |
|
fyi: I've pulled the newest code and traced the logs while changing the mode again: 
|
You're right... and I've found the property that holds this information: 0x4ecd And I also found some more properties: btw: just noticed, STROM_INVERTER and SPANNUNG_INVERTER needs accuracy_decimals 1 PS. where did you find this information? Can you send me that document? |
|
|
May be it is helpful.... Attached you will find 1hour log of my WPL13...I used the thz504.yaml Config
|
@adrai are you sure about that? What value is there in the display? IMO the type should be set to default (uint16_t) and with that accuracy_decimals is 0 resulting in e.g. 230V @ 5A |
The display shows 1 decimal 🤷♂️ |
oki doki, seems to be different on the THZ504 then ;) |
🤔 Wrong repo? 😅 |
omg... too many github projects 🤦♂️ and too early in the morning... sorry... deleted the comments |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.