An ebusd add-on

Third party integrations
104

See top tips 3 posts above…

105

But i dont understand how edit it. Now i have simple ebusd and create mqtt sensors template in HA, and then in in HA automatication i create an automatication to get value for this sensors and update it.

106

If what you have is working for then leave it. But to get the polling set up via your config files:

1 Like
107

But what mean to type number 1 to 9 ?

108

Please see above. 1-9 set priority of polling

109

But i can use for all high priority ?

110

Yeah, i have 8 different readings set at 1

111

In my opinion auto discovery no looks good. It found all entity as sensor… And example heating curve should be not found as sensor , it should be found as input to we can change value. Also other example should found climate for zone…
In multimatic integration with official gateway vaillant it works tha found climate for zone.

112

John30 has just released a new version of eBUSd.

https://github.com/john30/ebusd/releases/tag/v22.1

I’ll get a new version of the add-on uploaded in next few days

2 Likes
113

New release v22.1 :sparkler::fireworks:

22.1

BREAKING CHANGE - MQTT JSON and MQTT Discovery will be enabled after upgrade. This will break existing MQTT sensors

  • IMPROVE: Enable SSL
  • IMPROVE: Include MQTT integration cfg files (/etc/ebusd/mqtt-hassio.cfg)
  • IMPROVE: Add mqttint option
  • IMPROVE: Add mqtttopic option
  • IMPROVE: Add mqttvar option
  • IMPROVE: Enable MQTT discovery by default
  • IMPROVE: Align version number with eBUSd version
114

@afiwube Can you update opening post to reflect all recent changes please

116

Hey guys! Thanks for your time and effort on this addon! I installed the latest version and it works fine till now. I had some issues before with some connection problems (no signal…) and not updating values. I hope this addon will solve this.

What I want to aks you is the entities mqtt HA is discovering…John30 mentioned this in his post here.

I’m not that keen on mqtt and HA, relative noob and not an engineer or programmer and I could use some help please. How to get HA to create all the sensors and entities for each circuit?

I put quite a lot of time to manually configure sensors, switches, inputs, binary sensors for my vaillant heat pump and it’s been working great. I could even automate heatpump with my PV solar production system on the roof to heat water and load water tank. So I’m I don’t know how far this autodiscovery mqtt will go with the entities…
Thanks!

117

I did the upgrade to v22.1, and while it is certainly nice to have native support for HA in ebusd now, it’s not the most polished experience. After updating, I suddenly had close to 175 entities added to my HA-instance, most of which were not particularly useful.

A quick guide on how to solve this:

  1. In Configuration > Devices & Services > Entities: search for “ebus”

  2. Click the “Select all” checkbox just below the looking glass

    search-ebusd-entities
    search-ebusd-entities1236×288 14.4 KB

  3. Go through the list and uncheck the entities that you want to keep

  4. Click “Disable selected” to disable all entities that you are not interested in.

    disable-ebusd-entities
    disable-ebusd-entities1452×953 76.2 KB

  5. This filtered view is also very useful if you want to quickly edit the names into something more readable (great for the WAF!):

image
image823×545 24.3 KB

@timstanley1985, thank you for creating and maintaining this add-on!

118

If you want to revert to the old config and turn off auto discovery you can switch off MQTTJSON and change mqttinit to null.

I’m still playing with auto discovery - for example I removed any name fitters and tweaked mqtt-hassio.cfg so my reading for flame shows up as a binary_sensor as it defaulted to a sensor

119

I think the new auto discovery is a net improvement, so I’m happily keeping it :slight_smile:

I’ve adapted my MQTT HVAC entity as follows:

climate:
  - platform: mqtt
    name: CV
    max_temp: 25
    min_temp: 15
    precision: 0.1
    temp_step: 0.5

    action_topic: "ebusd/bai/Status01"
    action_template: "{{ (value_json['5'].value == 'on') | iif('heating', 'idle') }}"
    modes:
      - auto
      - heat
      - cool
      - "off"
    mode_state_template: >-
      {% set mode_values = { 'auto':'auto', 'on':'heat',  'night':'cool', 'summer':'off'} %}
      {{ mode_values[value_json['0'].value] | default('off') }}
    mode_state_topic: "ebusd/35000/Hc1OPMode"
    value_template: "{{ value_json.temp1.value }}"
    temperature_state_topic: "ebusd/35000/DisplayedHc1RoomTempDesired"
    temperature_low_state_topic: "ebusd/35000/Hc1NightTemp"
    temperature_high_state_topic: "ebusd/35000/Hc1DayTemp"

    current_temperature_topic: "ebusd/35000/DisplayedRoomTemp"
    current_temperature_template: "{{ value_json.temp.value }}"

I still need to figure out how I need to adapt the temperature_low_command_topic, temperature_low_command_template and the mqtt-hassio.cfg to be able to change the temperatures and modes again.

1 Like
120

Thanks @timstanley1985, I know I can go back but I really think this changes are on the right path and are putting ebusd on another level. The entiites (and circuits) appeard eventually :).

One more question, sorry if it’s stupid… where is mqtt-hassio.cfg file located in HA?

121

mqtt-hassio.cfg is at /etc/ebusd/mqtt-hassio.cfg within the ebusd container. If you want customise it run wget https://raw.githubusercontent.com/john30/ebusd/master/contrib/etc/ebusd/mqtt-hassio.cfg and then change the ebusd config to point to this file

2 Likes
122

Thank you @timstanley1985 !

123

have a strange issue, temperature values are presented like “HwcTempDesired = { “tempv”: {“value”: 6e+01}}” and rounded to full tens, when ebusctl read give proper value - 55 " # ebusctl read hwctempdesired
55"

124

Hi, does USB command sending work? I have a connection by USB.
Thanks for the addon, I send the tip :wink: