Hoe kan ik interfacen met Wifi van Toros Vision warmtepomp

[JoebarRC]

Sommige waardes bevatten een high en low bit, bv de kWh waardes.
In ESPHome een lambda berekening moeten doen

code:

(x >> 8) &0xFF

om de high bit te krijgen. Nu zijn alle waardes helemaal goed.
Hieronder een dashboard in ha, kan nu ook de setpoint van tapwater en de hysterese (de maxima daling van tapwater) met een slider schrijven naar de WP.
Enige wat niet kan is beïnvloeden wanneer de verwarming aangaat, dat loopt echt via de thermostaat en niet via modbus.. Maar…. Ik kan nu wel bv de set point van tapwater beïnvloeden en bv hoog zetten als de zon schijnt, dan zal de WP tapwater maken..
Voor de rest nog geen ideeen maar dit is al heel leuk

Dit is een compact dashboard, in de uitgebreide versie kan ik nu ook echt parameters aanpassen zoals in de microcom software.. Maar dat is echt voor debuggen en niet voor dagelijkse info

URL="https://tweakers.net/i/aJaFHXv-v5xHysMhBZEOzPO_udc=/fit-in/4000x4000/filters:no_upscale():strip_exif()/f/image/IKJ95lEMkqd3dQTWzb3mC2lL.png?f=user_large",,"1"][/URL]

[Bert-R]

Dat is een prachtig resultaat! Kan je delen wat je gebruikt om dit te doen, zowel qua hardware als configuratie?

[JoebarRC]

Oke, dit is het project tot nu toe, wat nog extra komt is een opentherm module en sketch zodat ik de thermostaat kan beïnvloeden. De modbus kan alles nu aansturen van de warmtepomp behalve de CV onderdelen want de toros heeft zelf geen idee van de temperatuur dat komt van de thermostaat.
Behalve dat is nu wel de toros te beïnvloeden op tapwater, je kan bv als er geen zon is de setpoint dynamisch verlagen zodat er geen tapwater gemaakt wordt en als de zon schijnt dit te verhogen. Werkt erg leuk

Dit is de electronica die gebruikt is, erg simpel, een esp32, een max485 bordje en een IR detector (ik heb er met 1 detector led) voor de kWH meter.



Als er geen communicatie is dan de aansluitingen A en B naar de modbus verwisselen. Ik moest ook uiteindelijk de 120ohm weerstand verwijderen, de bus had een te lage weerstand en slechte communicatie

Nu de ESPHome sketch;
Naast de modbus code gebruik ik ook een pulsmeter voor de kWh meter in de toros vision. Die code kan je natuurlijk verwijderen en heb je ook de extra bestanden niet nodig onder 'packages'

code:

# Toros Vision warmtepomp interface via Modbus en kWh pulsmeter

esphome:
  name: toros-modbuskwh
  min_version: 2024.11.0
  name_add_mac_suffix: false
  platform: ESP32
  board: nodemcu-32s #esp32dev  

packages:
 basis: !include ./components/basis.yaml
 updates: !include ./components/updates.yaml
 status: !include ./components/status_led.yaml
 pulse: !include ./components/pulse_meter.yaml
 
substitutions:
# Define the GPIO pins
  pulse_pin: GPIO5
  status_led: GPIO2 #D4
  friendly_name: WP Modbus kwh meter


# disable logging
logger:
  baud_rate: 0


# Enable Home Assistant API
api:

# Allow Over-The-Air updates
ota:
- platform: esphome

wifi:
  ssid: "Access Point SSID"
  password: "Access Point wachtwoord"

web_server:

uart:
  tx_pin: GPIO17
  rx_pin: GPIO16
  baud_rate: 19200

modbus:
  id: modbus1
  flow_control_pin: GPIO4

modbus_controller:
- id: modbus_device
  address: 0x1   ## address of the Modbus slave device on the bus
  modbus_id: modbus1
  setup_priority: -10
  update_interval: 30s
 
# Number (slider) input voor WP settings zoals de tapwater temperatuur
# hiermee kan misschien ook de switch functie gebruikt worden met modbus control om later te toggelen tussen temps bij zon bv.
number:
- platform: modbus_controller #template
  modbus_controller_id: modbus_device
  name: "Gewenste Tapwater temp"
  id: tapwater_setpoint_ha
  address: 0x817A
  register_type: holding
  value_type: U_WORD
  entity_category: config
  icon: mdi:chart-bell-curve
  min_value: 35
  max_value: 55
  step: 1
  mode: slider #box
  lambda: "return x; "
  write_lambda: |-
      return x;  

- platform: modbus_controller #template
  modbus_controller_id: modbus_device
  name: "Tapwater ECO minimum"
  id: tapwater_eco_setpoint_ha
  address: 0x8264
  register_type: holding
  value_type: U_WORD
  entity_category: config
  icon: mdi:chart-bell-curve
  min_value: 30
  max_value: 45
  step: 1
  mode: slider #box
  lambda: "return x; "
  write_lambda: |-
      return x;        
      
- platform: modbus_controller #template
  modbus_controller_id: modbus_device
  name: "Tapwater Max daling temp:"
  id: tapwater_hysterese_ha
  address: 0x817B
  register_type: holding
  value_type: U_WORD
  entity_category: config
  icon: mdi:chart-bell-curve
  min_value: 2
  max_value: 12
  step: 1
  mode: slider #box
  lambda: "return x; "
  write_lambda: |-
      return x;    

sensor:
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: status
    name: "Status WP"
    address: 0x539E
    register_type: holding
    value_type: U_WORD
      
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: zomer_winter_stand
    name: "Zomer-winter-stand. 0 = winter"
    address: 0x81E6
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: actual_error
    name: "Actuale storing"
    address: 0x0032
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: vergrendeld
    name: "Vergrendeld"
    address: 0x0032
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: lage_druk_schakelaar
    name: "Lage druk schakelaar"
    address: 0x30CE
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: hoge_druk_schakelaar
    name: "Hoge druk schakelaar"
    address: 0x30CE
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: max_t_cpr
    name: "MaxT CPR"
    address: 0xF12B
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: max_t_ee
    name: "MaxT EE"
    address: 0xF830
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: ec1
    name: "EC1"
    address: 0xF12A
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: ec2
    name: "EC2"
    address: 0xFA70
    register_type: holding
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: afgiftesysteem
    name: "Afgiftesysteem(min:sec)"
    address: 0xF37C
    register_type: holding
    unit_of_measurement: "sec"
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: pompen
    name: "Pompen(min:sec)"
    address: 0xF37A
    register_type: holding
    unit_of_measurement: "sec"
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: warmtepomp
    name: "Warmtepomp(sec)"
    address: 0xF364
    register_type: holding
    unit_of_measurement: "sec"
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: cpr_aan_aan
    name: "CPR AAN-AAN (min:sec)"
    address: 0xF37E
    register_type: holding
    unit_of_measurement: "sec"
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: cpr_uit_aan
    name: "CPR UIT_AAN (min:sec)"
    address: 0xF380
    register_type: holding
    unit_of_measurement: "sec"
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: cpr_aan_uit
    name: "CPR AAN-UIT(min:sec)"
    address: 0xF382
    register_type: holding
    unit_of_measurement: "sec"
    value_type: U_WORD
    accuracy_decimals: 0
    filters:
      - multiply: 1.0


  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: tbu_buiten_actueel
    name: "Temp Buitensensor"
    address: 0x35F7
    register_type: holding
    unit_of_measurement: "°C"
    value_type: U_WORD
    accuracy_decimals: 1
    filters:
      - multiply: 0.1

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: ttw_tapwater
    name: "Tapwater actueel"
    address: 0x3561
    register_type: holding
    unit_of_measurement: "°C"
    value_type: U_WORD
    accuracy_decimals: 1
    filters:
      - multiply: 0.1
  
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: tapwater_setpoint
    name: "Tapwater Gewenst"    
    address: 0x817A
    register_type: holding  
    unit_of_measurement: "°C"     
    value_type: U_WORD
    accuracy_decimals: 1
    
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: tapwater_eco_setpoint
    name: "Tapwater ECO minimum"    
    address: 0x8264
    register_type: holding  
    unit_of_measurement: "°C"     
    value_type: U_WORD
    accuracy_decimals: 1   
    
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: tapwater_hysterese
    name: "Tapwater Max Daling"    
    address: 0x817B
    register_type: holding  
    unit_of_measurement: "°C"      
    value_type: U_WORD
    accuracy_decimals: 1

  - platform: template
    id: tapwater_minimum_ha
    name: "Tapwater minimum temp"
    unit_of_measurement: "°C"
    lambda: "return id(tapwater_setpoint_ha).state - id(tapwater_hysterese).state;"

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: mengpositie_klep
    name: "Mengpositie klep (%)"
    address: 0x1DB6
    register_type: holding
    unit_of_measurement: "%"
    value_type: U_WORD
    accuracy_decimals: 1
    filters:
      - multiply: 1.0

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: tbr_bron_wp_in
    name: "TBR Bron WP IN"
    address: 0x5AAB
    register_type: holding
    unit_of_measurement: "C"
    value_type: U_WORD
    accuracy_decimals: 1
    filters:
      - multiply: 0.1

# de kWh registers bevatten waardes voor 2 parameters. De highbit van het d_WORD is nodig en wordt via de lambda berekend      
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: standby_kwh
    name: "kWh Standby"
    address: 0x5334
    register_type: holding
    unit_of_measurement: "kWh"
    value_type: U_WORD
    lambda: |-
      uint16_t value = x;    
      uint16_t highbit = (value >> 8) & 0xFF;
      return highbit;

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: tapwater_kwh
    name: "kWh Tapwater"
    address: 0x533B
    register_type: holding
    unit_of_measurement: "kWh"
    value_type: U_WORD
    lambda: |-
      uint16_t value = x;    
      uint16_t highbit = (value >> 8) & 0xFF;
      return highbit;    

# warmte kWh zit in de lowbits van het register.       
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: warmte_kwh
    name: "kWh Warmte"
    address: 0x5352
    register_type: holding
    unit_of_measurement: "kWh"
    value_type: U_WORD
    lambda: |-
      uint16_t value = x;    
      uint16_t lowbit = value & 0xFF;
      return lowbit;    

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: actief_koel_kWh
    name: "kWh Koel"
    address: 0x5361
    register_type: holding
    unit_of_measurement: "kWh"
    value_type: U_WORD
    lambda: |-
      uint16_t value = x;    
      uint16_t highbit = (value >> 8) & 0xFF;
      return highbit;    
        
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: passief_koel_kWh
    name: "kWh Koel passief"
    address: 0x535D
    register_type: holding
    unit_of_measurement: "kWh"
    value_type: U_WORD
    lambda: |-
      uint16_t value = x;    
      uint16_t lowbit = value & 0xFF;
      return lowbit;  
  
  
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: totaal_kwh
    name: "kWh Totaal"
    address: 0x6557
    register_type: holding
    unit_of_measurement: "kWh"
    value_type: U_WORD    

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: actief_tap_uren
    name: "Actief Tap Uren"
    address: 0x53C4
    register_type: holding
    unit_of_measurement: "uur"
    value_type: U_WORD   

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: actief_CV_uren
    name: "Actief CV Uren"
    address: 0x5532
    register_type: holding
    unit_of_measurement: "uur"
    value_type: U_WORD   
    
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: actief_koel_uren
    name: "Actief Koel Uren"
    address: 0x5597
    register_type: holding
    unit_of_measurement: "uur"
    value_type: U_WORD   

  - platform: modbus_controller
    modbus_controller_id: modbus_device
    id: passief_koel_uren
    name: "Passief Koel Uren"
    address: 0x5567
    register_type: holding
    unit_of_measurement: "uur"
    value_type: U_WORD   
            
# Vertalen van waardes naar tekst                
text_sensor:
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    name: "Status"
    id: status_string
    address: 0x539E
    register_type: holding        
    lambda: |-
      uint16_t value = id(status).state;
      switch (value) {
        case 1: return std::string("Stand-By");
        case 2: return std::string("Passief Tapwater");
        case 4: return std::string("Actief Tapwater voor");
        case 8: return std::string("Passief CV");
        case 16: return std::string("Actief CV voor");
        case 32: return std::string("Passief Koelen");
        case 64: return std::string("Regenereren");
        case 256: return std::string("Noodbedrijf TapW");
        case 512: return std::string("Noodbedrijf CV");
        case 1028: return std::string("Actief TapWater");
        case 1040: return std::string("Actief CV");
        default: return std::string("Unknown");
      }
      return x;
      
  - platform: modbus_controller
    modbus_controller_id: modbus_device
    name: "Seizoen"
    id: seizoen_string
    address: 0x81E6
    register_type: holding        
    lambda: |-
      uint16_t value = id(zomer_winter_stand).state;
      switch (value) {
        case 0: return std::string("Winter");
        case 1: return std::string("Zomer");
        default: return std::string("Unknown");
      }
      return x;

Nu de extra packages;
basis: !include ./components/basis.yaml
updates: !include ./components/updates.yaml
status: !include ./components/status_led.yaml
pulse: !include ./components/pulse_meter.yaml

updates.yaml

code:

# OTA configuration #
ota:
  - platform: esphome
    id: ota_esphome
  - platform: http_request
    id: ota_http_request

http_request:
  timeout: 10s
  verify_ssl: false

status_led.yaml

code:

light:
  - platform: status_led
    internal: true
    id: led_red
    pin: 
        number: ${status_led}
        inverted: true

basis.yaml

code:

# Basic configuration #
button:
  # Restart the ESP
  - platform: restart
    name: "Restart - WP kWh"

# Sensors for ESP version and WIFI information
text_sensor:
#   # Installed version
#   - platform: template
#     name: "Glow - Installed version"
#     id: glow_version
#     icon: "mdi:label-outline"
#     entity_category: diagnostic
#     lambda: |-
#       return {"${project_version}"};
#     update_interval: 6h
#   # ESPHome version
#   - platform: version
#     hide_timestamp: true
#     name: '${friendly_name} - ESPHome Version'
  # IP address and connected SSID
  - platform: wifi_info
    ip_address:
      name: '${friendly_name} - IP Address'
      icon: mdi:wifi
    ssid:
      name: '${friendly_name} - Connected SSID'
      icon: mdi:wifi-strength-2

sensor:
  # WiFi signal
  - platform: wifi_signal
    name: "${friendly_name} - WiFi Signal"
    update_interval: 120s

# Enable time component to reset energy at midnight
# https://esphome.io/components/time/homeassistant.html
time:
  - platform: homeassistant
    id: homeassistant_time

pulse_meter.yaml

code:

# Pulse meter configuration #

# Enable Home Assistant API
api:
  services:
    - service: reset_total_energy
      then:
        - button.press:
            id: button_reset_total

number:
  # Set the pulse rate of the LED on your meter
  - platform: template
    id: select_pulse_rate
    name: 'Puls rate - imp/kWh'
    optimistic: true
    mode: box
    min_value: 100
    max_value: 10000
    step: 100
    restore_value: yes
    initial_value: 800  

  # Reset total energy to given value
  - platform: template
    id: select_reset_total
    name: 'Reset Value - Total Energy kWh'
    entity_category: config
    optimistic: true
    mode: box
    min_value: 0
    max_value: 1000000
    step: 1
    initial_value: 985  # energie oude WP stond op 617kWh . 985 @28 maart 2025

button:
  # Reset the total energy entity
  - platform: template
    id: button_reset_total
    name: "Reset - Total Energy"
    on_press:
      - pulse_meter.set_total_pulses:
          id: sensor_energy_pulse_meter
          value: !lambda "return id(select_reset_total).state * id(select_pulse_rate).state;"

sensor:
  # Pulse meter
  - platform: pulse_meter
    id: sensor_energy_pulse_meter
    name: '${friendly_name} - Power Consumption'
    unit_of_measurement: W
    state_class: measurement
    device_class: power
    icon: mdi:flash-outline
    accuracy_decimals: 0
    pin: ${pulse_pin}
    internal_filter: 100ms # in theory 800 pulse per kwh, max around 6kWh peak would be 1.33 pulse per second. 1/1.33 = 730ms so starting with 100ms as filter  
    timeout: 1min
    on_raw_value:
      then:
        - light.turn_off:
            id: led_red
        - delay: 0.2s
        - light.turn_on:
            id: led_red
    filters:
      # multiply value = (60 / imp value) * 1000
      # - multiply: 60
      - lambda: return x * ((60.0 / id(select_pulse_rate).state) * 1000.0);
      # Update the sensor with an average every 10th second. See
      - throttle_average: 5s
      - filter_out: NaN
      - timeout: 60s  # sent value will be NaN
      - timeout:
            timeout: 60s
            value: !lambda return 3;      
      - clamp:
         min_value: 1
         max_value: 5500 # max Wh usage, eliminate spikes
         ignore_out_of_range: true     

    total:
      id: sensor_total_energy
      name: '${friendly_name} - Total Energy'
      unit_of_measurement: kWh
      icon: mdi:circle-slice-3
      state_class: total_increasing
      device_class: energy
      accuracy_decimals: 3
      filters:
        # multiply value = 1 / imp value
        # - multiply: 0.001
        - lambda: return x * (1.0 / id(select_pulse_rate).state);
        # Update the sensor once per 0.1 kWh consumed, or every 5th minute, whichever happens sooner.
        - delta: 0.01
        - heartbeat: 60s
      
  # Total day usage
  - platform: total_daily_energy
    id: sensor_total_daily_energy
    name: '${friendly_name} - Daily Energy'
    power_id: sensor_energy_pulse_meter
    restore: true
    unit_of_measurement: kWh
    icon: mdi:circle-slice-3
    state_class: total_increasing
    device_class: energy
    accuracy_decimals: 3
    filters:
      # Multiplication factor from W to kW is 0.001
      - multiply: 0.001

[ Voor 100% gewijzigd door JoebarRC op 08-04-2025 12:48 ]

[The Flying Dutchman]

Mooi gedaan!

Hou er rekening mee dat sommige waarden overflowen (kwh, aantal uren). Maximale waarde is 255. Ik geloof niet dat er ergens bijgeouden wordt hoe vaak de waarde over de kop is gegaan, dus dat zul je zelf moeten doen.

[Bert-R]

JoebarRC schreef op dinsdag 8 april 2025 @ 11:08:
Oke, dit is het project tot nu toe...

Dank je voor het delen! Na de zomer verwacht ik meer tijd en ga ik hier in duiken.