Ebusd 24.1.0 stops my communication

Third party integrations
1

After upgrading ebusd to version 24.1.0 my communication to my vaillant heatpump stoped working. I restored the backup version 23.2.5 and it worked again.

2

I had the same problem, but restoring the back up did not fix it.

Bit gutted as it was not simple to setup.

3

I also have quite some issues after upgrading to ebusd 24.1. I used to have 2 MQTT devices, one called b7v (which I believe corresponds to my Vaillant wireless thermostat) and another device called bai (which is my Vaillant gas heater). After 24.1, only the b7v device remained. Making matters worse, all my entities in the b7v device are renamed. For example, sensor.ebusd_b7v_hc1actualflowtempdesired_tempv became sensor.ebusd_b7v_hc1actualflowtempdesired which breaks all my dashboards, scripts and automations.

I restored a backup of ebusd (v23.2.6) and now I have my bai device back, but still all entity names have changed slightly. I noticed that my adapter says it is still on firmware 24.1, so I wonder if that is the reason why restoring only the ebusd add-on doesn’t work?

I also created an MQTT thermostat t control my heater, but that now also no longer works (even after restoring to ebusd v23.2.6). I think it might have to do with the 'tempv" which no longer appears in my entity names?

mqtt:
  climate:
    - name: Vaillant
      max_temp: 27
      min_temp: 15
      temp_step: 0.5
      modes:
        - auto
        - heat
        - "off"
      mode_state_template: >-
        {% set values = { 'auto':'auto', 'day':'heat', 'night':'cool', 'off':'off'} %}
        {% set state = value_json["opmode"].value %}
        {{ values[state] if state in values.keys() else 'off' }}
      mode_state_topic: "ebusd/b7v/z1OpMode"
      mode_command_template: >-
        {% set values = { 'auto':'auto', 'heat':'day', 'cool':'night', 'off':'off'} %}
        {{ values[value] if value in values.keys() else 'auto' }}
      mode_command_topic: "ebusd/b7v/z1OpMode/set"
      current_temperature_topic: "ebusd/b7v/z1RoomTemp"
      current_temperature_template: '{{value_json["tempv"].value}}'
      temperature_state_topic: "ebusd/b7v/z1ActualRoomTempDesired"
      temperature_state_template: '{{value_json["tempv"].value}}'
      temperature_low_state_topic: "ebusd/b7v/z1NightTemp"
      temperature_low_state_template: '{{value_json["tempv"].value}}'
      temperature_high_state_topic: "ebusd/b7v/z1DayTemp"
      temperature_high_state_template: '{{value_json["tempv"].value}}'
      temperature_low_command_topic: "ebusd/b7v/z1NightTemp/set"
      temperature_high_command_topic: "ebusd/b7v/z1DayTemp/set"

I’ll try to dig deeper this weekend, seems the 24.1 update did mess up quite a few things for me :slight_smile:

4

I managed to get it all working again on 23.2.6. I had to make a few modifications in my mqtt thermostats (some letters became capitals in the topic, and some of the value_json changed. Since it now works for me, I am going to stay on 23.26 for now.

5

You’re right; all my entity names have changed, too. I think I have everything working again now with the new sensor names, but unfortunately it’s left some weird readings in my historical data.

hopefully future updates don’t effect naming.

6

I had local config files and lost a number of entities moving to 24.1. Turns out several of the local config files needed updating and now it’s all working again. Apparently 24.1 puts more stringent demands on the config files.

7

What settings should we have a look at. I only have 4 lines in my config file
ebusd:
host: my-ip-ebusd-module
port: 9999
circuit: “700”