Ebus integration to control heating

[jacopsd]

I want to control my heating remotely using Home assistant, using ebus.

Hardware Setup:

• Heating = Weishaupt Heating system
• Connected via e-bus
• ebus USB dongle: eBus Koppler zur Verbindung von PC zum eBus Netzwerk mit USB Schnittstelle | IoT und Smart Home ESERA

Home Assistant:

• Latest supervisor 2021.10.8
• Latest core 2021.10.7

Installed Add-ons:

• ebusd An ebusd add-on
• MQTT Mosquito broker http://homeassistant2.local:8123/hassio/addon/core_mosquitto/info

Configuration:
Configured the ebusd to use USB:

Set up the log level to DEBUG to check what’s happening.

The LOG shows several errors:

> 2021-11-03 16:32:34.625 [update info] received MM cmd: 30f1050709bb038e030080ff65ff
> 2021-11-03 16:32:34.625 [update notice] received unknown MM cmd: 30f1050709bb038e030080ff65ff
> 2021-11-03 16:32:35.836 [bus debug] ERR: read timeout during receive command ACK, switching to skip
> 2021-11-03 16:32:35.933 [bus debug] ERR: read timeout during receive command ACK, switching to skip
> 2021-11-03 16:32:40.839 [main debug] performing regular tasks
> 2021-11-03 16:32:50.839 [main debug] performing regular tasks
> 2021-11-03 16:32:54.588 [update info] received MM cmd: 30f1050709bb038e030080ff65ff
> 2021-11-03 16:32:54.588 [update notice] received unknown MM cmd: 30f1050709bb038e030080ff65ff
> 2021-11-03 16:32:55.799 [bus debug] ERR: read timeout during receive command ACK, switching to skip
> 2021-11-03 16:32:55.896 [bus debug] ERR: read timeout during receive command ACK, switching to skip
> 2021-11-03 16:32:57.545 [update info] received BC cmd: f1fe500a0d01067fca5a5aff560007590538
> 2021-11-03 16:32:57.545 [update notice] received unknown BC cmd: f1fe500a0d01067fca5a5aff560007590538
> 2021-11-03 16:33:00.840 [main debug] performing regular tasks
> 2021-11-03 16:33:10.840 [main debug] performing regular tasks

… not sure if this is abnormal?

Now the questions are:

• How to proceed?
• I read all about ebusdctl commands but that command is not known on the HASS terminal? 5. Tools · john30/ebusd Wiki · GitHub

• How can I control the e-bus?
• How to link e-bus to MQTT?
• Is there some guidance here?
• And in the end: how to turn ON / OFF my heating?

Thank you for your help!

[jacopsd]

Some progress here:

• Seems not possible to use ebusctl from within HASS. Not clear why.
• Anyway, installed the ebusd and ebusctl on a separate linux box, and from there I can control the ebusd using ebusctl.
• The mosquito broker can be run on HASS as stated here: MQTT Broker - Home Assistant

Now the question is how to find the right commands to put my Weishaupt heating in day/night modus, and then glue all software components together.

All suggestions are welcome.

[afiwube (Lukas)]

hi @jacopsd, you can run ebusctl when you ssh into your home assistant installation.
ssh [email protected] -p 22222 (See Debugging the Home Assistant Operating System | Home Assistant Developer Docs)
from there you’ll need to get into the docker container running ebusd (supervisor adding are docker containers)
First run
docker ps
and take the ebusd container ID, then use that in
docker exec -it <id> /bin/bash
to run bash in the ebusd container.

you’ll be able to run ebusctl there.

regarding the log output:

> 2021-11-03 16:32:55.799 [bus debug] ERR: read timeout during receive command ACK, switching to skip

reads like you might need to adjust the ebus USB adapter threshold.

[afiwube (Lukas)]

@jacopsd

• The mosquito broker can be run on HASS as stated here: MQTT Broker - Home Assistant

Now the question is how to find the right commands to put my Weishaupt heating in day/night modus, and then glue all software components together.

Right, so you can interface with MQTT via Homeassistant config such as:

 - platform: mqtt
    name: "Warmwasser Zirkulations Pumpe"
    state_topic: "ebusd/hmu/StatusCirPump"
    value_template: "{{ value_json['0'].value }}"

As for Vendor(Weishaupt) specific commands, you’ll need to checkout the ebusd config and ebusd GitHub repositories and issues to see how far others have come with that. My self im getting some info from my Vaillant setup, but it’s not quite working out yet. Thinking about buying an off the shelf interface such as  SMART CONNECT KNX Vaillant - ise Individuelle Software und Elektronik GmbH and going an extra hoop through KNX.
I’ve also take a look at the Vaillant ISE interface’s software update to see if its possible to reverse engineer the ebus commands needed…

[jacopsd]

Concerning the ebus adaptor threshold: tried to tune using the screw on the ebus coupler. But this is extremely sensitive.

Did not succeed to get rid of all the errors, still these are there.
Would this be an issue?

2021-11-14 17:34:07.239 [main debug] performing regular tasks
2021-11-14 17:34:11.949 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-11-14 17:34:12.039 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-11-14 17:34:13.289 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-11-14 17:34:13.369 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-11-14 17:34:14.621 [update info] received BC cmd: 30fe0700090008ff341714110721
2021-11-14 17:34:14.622 [update notice] received update-read broadcast datetime QQ=30: 8.000;17:34:-;14.11.2021
2021-11-14 17:34:17.239 [main debug] performing regular tasks
2021-11-14 17:34:22.378 [update info] received MM cmd: 30f1050709550350020080ff65ff
2021-11-14 17:34:22.378 [update notice] received unknown MM cmd: 30f1050709550350020080ff65ff
2021-11-14 17:34:23.592 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-11-14 17:34:23.691 [bus debug] ERR: read timeout during receive command ACK, switching to skip
2021-11-14 17:34:27.239 [main debug] performing regular tasks```