Yuzu

[john30]

This is the 25th (="Y", therefor Yuzu) release of ebusd since it was completely reworked.

The major new features are mDNS-based device auto-discovery, the switch of default config path to ebus.github.io generated from TypeSpec sources, additional commands for device simulation and testing, as well as a bunch of bug fixes.

See ChangeLog and Wiki for details.

Debian 12 (Bookworm), 11 (Bullseye), and 10 (Buster) install packages for amd64, 386, armv7 (Raspberry Pi 2/3/4), and arm64 (Raspberry Pi 3/4 64 bit) are attached and will also be made available soon in the Debian repository as described here.

For convenience, an armv6l (Raspberry Pi 1 and Zero/Zero W) Buster image is attached here as well (not part of the Debian repository though).

Variants of each binary with MQTT support have an additional "mqtt1" (for libmosquitto1) suffix in the name, whereas those without don't.

For Arch Linux, simply run makepkg in the contrib/archlinux/ebusd/ directory.

The latest release is also available as multi-architecture Docker image on the hub with tag ebusd:latest.

---

This discussion was created from the release Yuzu.

[hemagi]

Hi John, due to mDNS, is is safe to upgrade 23.2 to 24.1 without changing the configuration?

I am using a viallant heat pump, and ebusctl i states that the CSVs have changed:

update check: version 24.1 available, broadcast.csv: newer version available, vaillant/08.ehp.csv: newer version available, vaillant/15.uih.csv: newer version available, vaillant/timer.inc: newer version available, vaillant/yield8485.inc: newer version available

Is this due to change of location of the config files, or has their content changed?

[john30]

mdns is just a new option, so of course you can still assign the device string manually.

for the second question, see the changelog

[Mozzarella7]

Hi John,
is it possible to keep TypeSpec source file locally as in "old" version using EBUSD_CONFIGPATH parameter.
If yes I understand that all I need is in /master/src catalog.

Thank you for the continuous development of this project!

[john30]

the local use of newly generated csv from typespec is described in the readme

[leonundjulie]

Hi John. However, I noticed the available update to the actual one 24.1 not before :-( About this I Need to know how the update procedure hast to be performed? Do I have to uninstall the previous version first? Or can I use the new version as with the first installation, i.e. simply overwrite the first version?

[john30]

that depends entirely on the way of using it, i.e. docker, local install, managed HA addone etc.
for debian package it works just like any other, for docker a pull and recreate of the container is enough

[leonundjulie]

@john30 , my mistake … I am operating a Raspberry 4 with 64 Bit bookworm OS

[leonundjulie]

/ @john30 , what is going wrong. I am operating a RASPBERRY PI 4 with a 64Bit bookworm OS. What is my mistake Düring my Installation?

The Photo Shows the Data of my PI:

This Photo Show what happened during the Installation process:

[john30]

looks as if the URL you used is invalid

[leonundjulie]

Thanks for your Replikation. And indead, I made copy mistake. However, I can Not Check before today evening due to limited possibilities to connect my PI remotely.

[Pamirkr]

Hi John, I have a problem with running this version of ebusd with mqtt user's password option. I tried starting ebus as a service and input password in /etc/default/ebus file. Also I tried running ebusd directly from CLI:

root@wyse:~# ebusd --mqtthost=192.168.1.101 --mqttport=1883 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqttjson --mqttuser=ebus --mqttpass=ebus

But result is the same. Null password is sent to MQTT broker and connection is refused. Any idea where I make a mistake?

Ebus configuration file:

Ebusd service status:

Ebusd log:

Log from Mosquitto broker:

[Koky05]

Did you create that ebus user under MQTT broker?

[Pamirkr]

Yes, I did. I also found the cause of the problem. I did not notice that there were other ebusd processes running in the background without user and password set for MQTT. After killing them connection with mqtt broker works.