[eBUS 2.0] New binding - Release Candidate 4

ebus
binding
Tags: #<Tag:0x00007f51dfb23580> #<Tag:0x00007f51dfb27f40>

(Allodo) #383

Hi,

till now I’ve no success with Autodiscovery of my boiler :frowning:

Is it possible that I have to change Master and Slaveaddress?

Here is my ebusctl info from FHEM

version: ebusd 3.1.v3.1-22-gdaf771e
update check: revision v3.1-1-g60a18d1 available, broadcast
csv: different version available
access: *
signal: acquired
symbol rate: 25
max symbol rate: 169
reconnects: 1
masters: 3
messages: 13
conditional: 0
poll: 0
update: 4
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=V3x00;SW=011;HW=9902"
address 10: master #2
address 31: master #8, ebusd
address 46, master #8, ebusd

ebusctl scan result
08;Vaillant;V3x00;0118;9902

At moment my ebus-adapter is disconnected to FHEM, so that it is free for OH2 :wink:
Or do I still need other Config-Files?


(csowada) #384

So, Autodiscovery finds nothing or only not your Vaillant device. This binding has only a subset of devices compared to to ebusd. Can give us the device type ?


(csowada) #385

Hello @Stefaan_Vandevelde,

I’ve released a new version, you should try it with this version. But you defined the thing by hand, a VRCxxx device with slave address 08, but your ebusd log shows 15. Could you try this, if auto discovery fails. Slave address 08 is for BAI things as far as I know.


(Vincent Regaud) #386

Hello there, does anyone knows how to order the board for the ebus adapter, please?


(Allodo) #387

@csowada
Autodiscovery finds nothing, so I’ve to add Things manually :frowning:

Here ist what ebusctl info says after I connected it with FHEM:

version: ebusd 3.1.v3.1-22-gdaf771e
update check: revision v3.1-1-g60a18d1 available, broadcast
csv: different version available
access: *
signal: acquired
symbol rate: 40
max symbol rate: 95
min arbitration micros: 62
max arbitration micros: 298
min symbol latency: 5
max symbol latency: 39
reconnects: 0
masters: 3
messages: 13
conditional: 0
poll: 0
update: 4
address 03: master #11
address 08: slave #11, scanned "MF=Vaillant;ID=V3x00;SW=011;HW=9902"
address 10: master #2
address 15: slave #2, scanned "MF-Vaillant;ID=47000, SW=0420;HW=1403"
address 31: master #8, ebusd
address 36: master #8, ebusd

ebusctl scan result
08;Vaillant;V3x00;0118;9902
15;Vaillant;47000;0420;1403


(csowada) #388

Hello @Allodo,

can you send me a complete log file from a fresh openhab start, so it contains 5-10min. You can send it via PM, if it contains sensitive information.


(Allodo) #389

I’ve now stopped ebusd on my FHEM-RPi so that ebus-adapter will be free and rebooted my other RPi with OH2 over VPN. When I will be at home I could send you the complete log file.

EDIT:
It’s really crazy, after I deleted now the ebus-bridge an added new, now something was found automatically und I get data :slight_smile:

ebus1


(Allodo) #390

ebus2


(Stefaan Vandevelde) #391

@csowada,
What do you mean exactly with “But you defined the thing by hand” ? I disabled the .thing file and followed the configuration instructions the github readme. Is there another way ?
Right now, there is only the Vaillant bai and the Tado extension kit on the ebus (also the ebus bridge of course).
I will try to install the newer version, see if that helps.
In meantime, I got some more error logs. Maybe this gives you more insight

05:48:11.717 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
05:48:11.743 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
05:48:11.780 [DEBUG] [de.csdev.ebus.core.EBusController    ] - Send: FF 15 07 04 00 0B @ 0. attempt
05:48:11.809 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send FF
05:48:11.831 [DEBUG] [de.csdev.ebus.core.EBusController    ] - eBUS collision with SYN detected!
05:48:11.860 [TRACE] [de.csdev.ebus.core.EBusController    ] - Priority class doesn't match, blocked for next SYN ...
05:48:11.894 [DEBUG] [de.csdev.ebus.core.EBusController    ] - Send: FF 15 07 04 00 0B @ 1. attempt
05:48:11.946 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send FF
05:48:11.968 [DEBUG] [de.csdev.ebus.core.EBusController    ] - eBUS collision with SYN detected!
05:48:11.995 [TRACE] [de.csdev.ebus.core.EBusController    ] - Priority class doesn't match, blocked for next SYN ...
05:48:12.028 [DEBUG] [de.csdev.ebus.core.EBusController    ] - Send: FF 15 07 04 00 0B @ 2. attempt
05:48:12.074 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send FF
05:48:12.105 [DEBUG] [de.csdev.ebus.core.EBusController    ] - eBUS collision with SYN detected!
05:48:12.133 [TRACE] [de.csdev.ebus.core.EBusController    ] - Priority class doesn't match, blocked for next SYN ...
05:48:12.166 [DEBUG] [de.csdev.ebus.core.EBusController    ] - Send: FF 15 07 04 00 0B @ 3. attempt
05:48:12.194 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send FF
05:48:12.225 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 15
05:48:12.246 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 07
05:48:12.268 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 04
05:48:12.289 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 00
05:48:12.310 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 0B
05:48:12.332 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Received SYN byte while receiving telegram! [ERROR: INVALID_SYN, DATA: FF AA]
05:48:12.345 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Unable to send telegram FF 15 07 04 00 0B after 2 attempts ... [ERROR: TOO_MANY_ATTEMPS, DATA: FF 15 07 04 00 0B]
05:48:12.345 [DEBUG] [de.csdev.ebus.core.EBusController    ] - Send: FF 08 07 04 00 51 @ 0. attempt
05:48:12.463 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send FF
05:48:12.494 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 08
05:48:12.516 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 07
05:48:12.537 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 04
05:48:12.559 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 00
05:48:12.581 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 51
05:48:12.612 [TRACE] [de.csdev.ebus.core.EBusController    ] - Waiting for slave answer ...
05:48:13.195 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: FF 08 07 04 00 51]
05:48:13.195 [DEBUG] [de.csdev.ebus.core.EBusController    ] - Send: FF 08 07 04 00 51 @ 1. attempt
05:48:13.294 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send FF
05:48:13.316 [DEBUG] [de.csdev.ebus.core.EBusController    ] - eBUS collision detected! 0x00
05:48:13.343 [TRACE] [de.csdev.ebus.core.EBusController    ] - Priority class doesn't match, blocked for next SYN ...
05:48:13.376 [DEBUG] [de.csdev.ebus.core.EBusController    ] - Send: FF 08 07 04 00 51 @ 2. attempt
05:48:13.404 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send FF
05:48:13.436 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 08
05:48:13.458 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 07
05:48:13.480 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 04
05:48:13.502 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 00
05:48:13.524 [TRACE] [de.csdev.ebus.core.EBusController    ] - Send 51
05:48:13.556 [TRACE] [de.csdev.ebus.core.EBusController    ] - Waiting for slave answer ...
05:48:14.056 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
05:48:14.056 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: FF 08 07 04 00 51]
05:48:14.056 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; Unable to send telegram FF 08 07 04 00 51 after 2 attempts ... [ERROR: TOO_MANY_ATTEMPS, DATA: FF 08 07 04 00 51]
05:48:14.091 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
05:48:14.228 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
05:48:14.228 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 12 07 04 00 4C]

(Stefaan Vandevelde) #392

@csowada,
I get below error messages in the log after installing the latest version 18 and creating a bridge thing, before adding the bai thing.

06:38:25.422 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
06:38:25.507 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
06:38:25.808 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:38:26.367 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
06:38:26.414 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
06:38:26.803 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:38:27.812 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:38:30.849 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:38:32.828 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:38:33.814 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:38:34.319 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 0A 07 04 00 AB]
06:38:34.844 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:38:35.414 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
06:38:35.468 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
06:38:35.806 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...

After creating the bai thing from the inbox in PaperUI and creating two items, I get the below logs

06:48:34.386 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - eBUS telegram error; No response from slave! AA [ERROR: NO_SLAVE_RESPONSE, DATA: 10 1C 07 04 00 4E]
06:48:34.865 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:48:35.445 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata
06:48:35.491 [TRACE] [nhab.binding.ebus.handler.EBusHandler] - eBUS node handler ebus:std:71c1289c:08 use collectionId std, not bai ...
06:48:35.534 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata from 10 to 08 ...
06:48:35.875 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:48:36.435 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - Received telegram from address 10 to 08 with command boiler.control.getopdata.02
06:48:36.481 [TRACE] [nhab.binding.ebus.handler.EBusHandler] - eBUS node handler ebus:std:71c1289c:08 use collectionId std, not bai ...
06:48:36.525 [DEBUG] [inding.ebus.handler.EBusBridgeHandler] - No handler has accepted the command boiler.control.getopdata.02 from 10 to 08 ...
06:48:36.874 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...
06:48:37.884 [TRACE] [de.csdev.ebus.core.EBusController    ] - waiting for slave answer ...

None of the items is getting any value, they remain ‘Nan’.


(csowada) #393

Hello @Stefaan_Vandevelde,

maybe the master address is still in use by another device link your Tado? You should try 00 or FF for your bridge.


(Stefaan Vandevelde) #394

@csowada, how/where can I change the master address ? Is it a setting in the ebus binding ?


(csowada) #395

Hello @Stefaan_Vandevelde,

its an advance setting in the bridge settings page in PaperUI. Or the binding setting? I’m not sure yet. Should be easy to find.


(Vincent Regaud) #396

Hello there, does anyone knows how to order the board for the ebus adapter, please?
The FHEM forum is in German and not very friendly with the translator
Thanks


(Benjamin) #397

Hi,

how can i test the Brutforce analyzer to find some new values ?

Benny


(Cernon) #398

Hello,

I Try out your binding since December. It works fine. Now my openhab crash and I have to install everything new. I upgrade to Openhab 2.3 unstable Build 1268. Now I get in Papier UI an error:
UNINITIALIZED - HANDLER_INITIALIZING_ERROR linkRegistry
and nothing works.
How can I solve this? I read some discussion about removing “linkRegistry”?!?


(csowada) #399

This is new for me. Can you send a log. I use 2.2 stable in production and an older 2.3 snapshot for development.


(csowada) #400

Its just a internal Java class, no console command yet. So only useful as a developer.


(Allodo) #401

Since my ebus binding is working I now wanna see some values. But there are a lot of Items who don’t delivers any values. So my first step, get Item an wait if there is an value. But this method isn’t really nice.

Is there a possibility to list all values? So I can pick them up and make not try & error?

Maybe something like _ebusctl find -d under fhem?


(Cernon) #402

in PaperUI you can use the Simple mode for Items in den system-config. Then all items of a new thing where automatically aktiv and you can see the value in “control”