EBUS Wolf cgb-2 - Device identification

[checkmann (Christoph)]

Hi all,
I’ve made the ebus adapter 2.2 for the rpi to work (https://ebus.github.io/adapter/raspberrypi) with the latest ebus binding ([eBUS 2.0] New binding - Release Candidate 7b).
Directly after the bridge was working correctly, serveral things have been found automatically (ebus standard).

1. Here is my first question: since I’m having a Wolf cgb-2 with solar, BM, … I don’t understand why the deivces are classified as ebus standard. Is this correct?

For me the ebus stats are looking somehow OK.

Each ebus stanard thing is having same units (e.g. Exhaust temperatur, DHW lead water temperature, …), but I don’t get any information by linking these items.
2) second question: How do I know, which Address is which device on the bus?
I’ve 08,15,35,50,51,75,76,F6 as ebus standard things

3. how can I get or set any values? e.g. I want to change the heating mode?

[csowada]

You should try the latest version from here

eBUS Binding 3.x [3.4.0;3.9.9)

[ebus] With this binding, heating and ventilation systems that have an eBUS can be addressed. The corresponding hardware is required. Connections are possible via serial, TCP and ebusd. Requirements openHAB 3.x eBUS Hardware Interface (Serial, Ethernet, ebusd) eBUS protocol compatible Heating System Documentation Binding Readme Download Release 3.4.16 Release 4.0.18 or just check GitHub Releases for the latest or older versions. Changelogs

But could you send your current device table from the console?

ebus devices

it should show something like

MA | SA | Identifier     | Device         | Manufacture               | ID | Firmware   | Hardware   | Last Activity
---+----+----------------+----------------+----------------------+----+------------+------------+---------------------
00 | 05 |                | <interface>    | eBUS Library              |    | null       | null       | ---
   | 50 | 01 21 00 5A 00 | mm1            | Wolf GmbH                 | 19 | 60.01      | 0          | Mon Jan 13 22:28:37 CET 2020
FF | 04 |                | ---            | null                      |    | null       | null       | Mon Jan 13 22:28:27 CET 2020
30 | 35 | 00 20 00 00 C0 | bm2            | Wolf GmbH                 | 19 | 2.04       | 0          | Mon Jan 13 22:28:37 CET 2020
00 | 05 |                | <interface>    | eBUS Library              |    | null       | null       | Mon Jan 13 22:28:34 CET 2020
71 | 76 | 01 15 00 00 80 | sm1            | G. Kromschröder AG        | 50 | 2.27       | null       | Mon Jan 13 22:28:33 CET 2020
03 | 08 | 01 21 00 5A 40 | cgb2           | Wolf GmbH                 | 19 | 60.01      | 0          | Mon Jan 13 22:28:36 CET 2020
F1 | F6 |                | ---            | null                      |    | null       | null       | Mon Jan 13 22:28:37 CET 2020
----------------------------------------------------------------------------------------------------------------------
MA = Master Address / SA = Slave Address / ID = Manufacture ID

[checkmann (Christoph)]

Thanks csowada!
I’ve now updated the plugin to the latest version (2.5.1-2).
Same behaviour up until now.
If I run ebus devices, I got:

MA | SA | Identifier     | Device         | Manufacture               | ID | Firmware   | Hardware   | Last Activity
---+----+----------------+----------------+----------------------+----+------------+------------+---------------------
FF | 04 |                | <interface>    | eBUS Library              |    | null       | null       | ---
   | 50 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:38:00 CET 2020
   | 51 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:38:01 CET 2020
30 | 35 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:38:01 CET 2020
10 | 15 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:38:03 CET 2020
70 | 75 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:38:01 CET 2020
71 | 76 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:37:55 CET 2020
03 | 08 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:38:03 CET 2020
F1 | F6 |                | ---            | null                      |    | null       | null       | Tue Jan 14 21:37:59 CET 2020
----------------------------------------------------------------------------------------------------------------------

Any idea?

[csowada]

Mh, not so good. DO you use a special serial ebus driver? I’m not sure, I think we had such issue in the old thread. Have you tried the other serial driver from the binding? Is it working with ebusd? This is also an option. You can try to manually create Wolf things based on my device list.

[csowada]

But you should enable logging for the binding. In most cases you should start with

log:set DEBUG de.csdev.ebus or
log:set TRACE de.csdev.ebus

I expect some send issue in the log. This could be the reason why auto discovery is not working.

[checkmann (Christoph)]

1. This was a swift reply csowada, thanks again!
   Indeed I’m using a special serial ebus driver (https://github.com/eBUS/ttyebus) which is necessary with this rpi ebus adapter (https://ebus.github.io/adapter/raspberrypi.en.html).
   I will try to test within the next days with standard serial interface.
   Just out of my curiosity: which ebus adapter is commonly used here?

2. If I would try to add the the things manually, how do I know which ID correspond to which device? e.g. ID65 is WOLF SM1, WOLF BM, …?

[csowada]

You can use the master or slave address (not sure) from my table to identify the things in your setup.

[checkmann (Christoph)]

I’ve made some little progress with a serial ebus adapter.
now my ebus device list is looking like this
openhab> ebus devices

MA | SA | Identifier     | Device         | Manufacture               | ID | Firmware   | Hardware   | Last Activity
---+----+----------------+----------------+----------------------+----+------------+------------+---------------------
FF | 04 |                | <interface>    | eBUS Library              |    | null       | null       | ---
   | 50 | 01 14 00 18 00 | ---            | G. Kromschröder AG        | 50 | 2.08       | null       | Wed Jan 15 23:22:20 CET 2020
   | 51 | 01 14 00 18 00 | ---            | G. Kromschröder AG        | 50 | 2.08       | null       | Wed Jan 15 23:22:21 CET 2020
10 | 15 |                | ---            | null                      |    | null       | null       | Wed Jan 15 23:22:23 CET 2020
30 | 35 |                | ---            | null                      |    | null       | null       | Wed Jan 15 23:22:20 CET 2020
70 | 75 |                | ---            | null                      |    | null       | null       | Wed Jan 15 23:22:21 CET 2020
71 | 76 | 01 15 00 00 80 | sm1            | G. Kromschröder AG        | 50 | 2.27       | null       | Wed Jan 15 23:22:25 CET 2020
03 | 08 | 01 06 33 42 02 | ---            | G. Kromschröder AG        | 50 | null       | 51.3       | Wed Jan 15 23:22:23 CET 2020
F1 | F6 |                | ---            | null                      |    | null       | null       | Wed Jan 15 23:22:24 CET 2020
07 | 0C |                | ---            | null                      |    | null       | null       | Wed Jan 15 23:10:33 CET 2020

---

However, I’m not able to get any proper values from the bus. The only value that can be read is
Temperature, solar cylinder 1 - 15.8°C which seem to be correct.
I’m trying to read e.g. Burner hours run from the Wolf CGB-2 (Slave 08) without success

Sometimes I see in the log
2020-01-15 23:37:21.338 [DEBUG] [.csdev.ebus.command.EBusCommandUtils] - Value temp_mixer with -100 is smaller then allowed 100

Any help / ideas?

[Jordan74 (Jens Jordan)]

If I run ebus devices on my installation, I got:

MA | SA | Identifier     | Device         | Manufacture               | ID | Firmware   | Hardware   | Last Activity
---+----+----------------+----------------+----------------------+----+------------+------------+---------------------
FF | 04 |                | <interface>    | eBUS Library              |    | null       | null       | ---
   | 51 | 01 14 00 10 00 | ---            | G. Kromschröder AG        | 50 | 2.08       | null       | Wed Feb 26 10:25:41 CET 2020
FF | 04 |                | <interface>    | eBUS Library              |    | null       | null       | Wed Feb 26 10:25:45 CET 2020
30 | 35 | 00 20 00 00 C0 | bm2            | Wolf GmbH                 | 19 | 2.04       | 0          | Wed Feb 26 10:25:47 CET 2020
70 | 75 |                | ---            | null                      |    | null       | null       | Wed Feb 26 10:22:13 CET 2020
03 | 08 | 01 21 00 5A 40 | cgb2           | Wolf GmbH                 | 19 | 40.01      | 0          | Wed Feb 26 10:25:45 CET 2020
F1 | F6 |                | ---            | null                      |    | null       | null       | Wed Feb 26 10:25:49 CET 2020
   | 85 | 00 20 00 00 C0 | bm2            | Wolf GmbH                 | 19 | 2.04       | 0          | Wed Feb 26 10:25:19 CET 2020
----------------------------------------------------------------------------------------------------------------------

And here you will find my ebus.things definition. May you can double-check it with your ebus.things definition.

//Bridge ebus:bridge:heating "eBUS Bridge (serial)" @ "eBus" [ serialPort="/dev/ttyUSB0", serialPortDriver="nrjavaserial", advancedLogging=false ]
Bridge ebus:bridge:heating "eBUS Bridge (ebusd)" @ "eBus" [ ipAddress="127.0.0.1", port=8888, networkDriver="ebusd", masterAddress="FF", advancedLogging=false ]
{
    Thing cgb2 08 "Wolf CGB-2 (0x08)" @ "eBus" [ slaveAddress="08" ]
    {
        Channels:
        Type cgb2_boiler_modulation_modulation : cgb2_boiler_modulation#modulation
        Type cgb2_boiler_pressure_pressure     : cgb2_boiler_pressure#pressure
        Type cgb2_dhw_temp-flow_temp-flow      : cgb2_dhw_temp-flow#temp-flow
        Type cgb2_dhw_temp-return_temp-return  : cgb2_dhw_temp-return#temp-return
    }
    Thing std F6 "eBUS Standard (0xF6)" @ "eBus" [ slaveAddress="F6" ]
    {
        Channels:
        Type std_controller_d-values-rc2_temp-outside : std_controller_d-values-rc2#temp-outside
    }
    Thing mm1 51 "Wolf Mischer Modul (0x51)" @ "eBus" [ slaveAddress="51" ]
    {
        Channels:
        Type mm1_mixer_data1_temp-mixer : mm1_mixer_data1#temp-mixer
    }
    Thing bm2 35 "Wolf BM-2 (0x35)" @ "eBus" [ slaveAddress="35" ]
    {
        Channels:
        Type bm2_heating_program-heating-circuit_program : bm2_heating_program-heating-circuit#program 
        Type bm2_dhw_program-dhw-circuit_program : bm2_dhw_program-dhw-circuit#program
    }
    Thing bm2 85 "Wolf BM-2 (0x85)" @ "eBus" [ slaveAddress="85", masterAddress="80" ]
    {
        Channels:
        Type bm2_heating_program-heating-circuit_program : bm2_heating_program-heating-circuit#program 
    }
}

At the moment I don’t know, why for the slave address 0x51 and 0x85 no master address is set?