eBUS Pre-Release for 1.8.0

So for example
Level_modulation is not the modulation level. In the manual it says part load heating, but it’s a value to limit the maximum kw of the boiler. The current id would make someone think it’s a value that changes depending on the current modulation level, but it’s not.
Would level_partload then make sense?

Temp_exhaust would make me think of the temperature in the flue gas exhaust. But it’s just the water outlet temperature. In my case it’s always the same as the flow temperature, but maybe the value could be different in other versions. Temp_outlet would be more suitable in my opinion.

Taking into account your comment, diverter valve should probably be state_divertervalve then?

For wolf you use level_modulation and modulation_pump which isn’t really consistent. I suggestto either use boiler.modulation and boiler.modulation_pump or to use boiler.level_modulation and boiler.level_modulation_pump.

The others are fine for me.

Okay, you are totaly right I tought it would be the current modulation, not the maximum settings.

Wrong translated to german :wink: , I tought this is the exhaust temp.

Yes, but I would write state_diverter_valve, easier to read

And again, you are right. This is not consequent. I will change this.

I’m so happy that you are helping me to build up a great binding. I waited for so long to get help with the vaillant devices. And now I see a well running binding, that can be released as a stable version.

BTW: The binding now is compatible with openHAB 2.0. I will look on openHAB 2.0 over christmas to check the new platform. Maybe I’ll write a version 2.0 from scratch to use the bridge mode, discovery etc. (No changes on json configurations ;-))

Thanks for the nice binding it is promising! The 1.7 was not able to connect but this one does :smile:

Any idea what “EBus telegram sender-crc invalid, skip data!” means? And how to solve.

2015-12-25 08:17:45.243 [DEBUG] [.ebus.internal.parser.Analyses] - 00 00 00 00 00 00 00 00 00 F5 AA
2015-12-25 08:17:45.243 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-25 08:17:45.922 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: AE 00 00 00 08 12 00 00 10 00 D5 D4 D5 00 00 00 00 00 00 00 04 00 00 FD AA
2015-12-25 08:17:46.330 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: 00 46 00 00 00 00 08 80 00 00 00 00 00 00 00 00 00 00 00 00 00 D5 D5 D5 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 F1 F5 AA
2015-12-25 08:17:47.285 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: AB 00 00 00 12 00 00 00 00 00 00 00 00 00 00 01 21 F8 AE D5 D5 D5 D7 DD EA DF AE D5 D5 AE 00 00 00 00 00 00 00 00 00 D5 F7 AB 00 00 00 00 00 41 00 00 00 A8 AA
2015-12-25 08:17:47.764 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: D5 D5 00 02 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 AA
2015-12-25 08:17:48.562 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: AB AB D7 F5 F5 EB D5 BA BE D5 D5 D5 BB AA
2015-12-25 08:17:49.520 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: AE FD F5 F5 BB FD AB F5 D5 FF BA AE F7 EA D5 DD AF AA
2015-12-25 08:17:49.881 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: D5 F7 BA F5 AB EA F5 A9 AA
2015-12-25 08:17:50.307 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: AE 01 00 7E 00 00 22 00 00 00 00 00 FB F5 00 00 20 00 00 00 91 00 00 D5 30 00 6A 00 00 24 00 00 00 00 12 00 00 FE D5 AA
2015-12-25 08:17:50.667 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: BE BA 15 00 00 00 00 00 01 00 00 00 AA
2015-12-25 08:17:51.146 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: F5 85 00 00 00 00 01 00 00 00 24 D4 D5 EB AA
2015-12-25 08:17:51.425 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: F5 D5 EF 81 BA AE AA
2015-12-25 08:17:51.904 [WARN ] [.ebus.internal.utils.EBusUtils] - EBus telegram sender-crc invalid, skip data! Data: FA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Thnks

@csowada Here the updated vrc430 config file where the day setpoint was updated (see remark by @Tomek in other thread).
vaillant-vrc430-configuration.json (7.1 KB)

@bajan Sometimes I also get invalid crc’s, but your data doesn’t really look as it should.
In another thread I also saw that you are using a vrc630 and vr90, so I started a config file with a few items. So once you get it working, it would be great if you could test these.
vaillant-vr90-configuration.json (1.3 KB)
vaillant-vrc630-configuration.json (2.8 KB)

1 Like

Hallo @nikoraes
Thanks for update json file.
I spen last few hours try to use new ebus binding form https://github.com/csowada/openhab/releases/tag/1.8.0RC5ETH
but no success…
Here is my openhab,cfg
ebus:parserUrl=platform:/base/…/configurations/ebus-config.json
ebus:parsers=vaillant-vrc430,custom

(I renamed vaillant-vrc430-configuration.json from your post to ebus-config.json)
my items file looks like this
Number e_DHW_Program “DHW Operation mode[%s]” (Vaillant) { ebus=“id:dhw.program_dhw_circuit, cmd:dhw.program_dhw_circuit, dst:15, refresh:300, set:dhw.set_program_dh
w_circuit.program_dhw_circuit” }

But it docent work… I can’t set new value
in log file i get
2015-12-25 14:40:45.555 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - Unable to set value key “program_dhw_circuit” in command “dhw.set_program_dhw_circuit.{}”, can’t compose telegram …

Can you tell me what I did wrong ?
Regards
Tomek

I shure wil test and already thnks for your effort and time!
Do you have any clue what the invalid CRC means? I already treyed to adjust the Ebus but it doesn 't change anything.

Thnks

Hello All
I have created new items file for ebus 1.8RC6 bindigs
Number e_Temp_Zew “Outside temperature [%.1f °C]” { ebus=“id:controller.temp_outside.temp_outside, cmd:controller.temp_outside, dst:15, refresh:300” }
Number e_Temp_Room "Room temperature [%.1f °C] { ebus=“id:controller.temp_room_disp.temp_room_disp, cmd:controller.temp_room_disp, dst:15, refresh:300” }
Number e_Temp_Room_Dis “Dis Room temperature [%.1f °C]” { ebus=“id:controller.temp_room.temp_room, cmd:controller.temp_room, dst:15, refresh300” }
Number e_HC1_Program"HC1prog[%s]”{ ebus="id:heating.program_heating_circuit,cmd:heating.program_heating_circuit,refresh120,set:heating.set_program_heating_circuit.program_heating_circuit,dst:15”}
Number e_DHW_Program “DHW Operation mode[%s]” { ebus=“id:dhw.program_dhw_circuit, cmd:dhw.program_dhw_circuit, refresh:120, set:dhw.set_program_dhw_circuit.program_dhw_circuit, dst:15” }
Number e_DHW_Temp_Act “DHW Actual temp [%.1f °C]” { ebus=“id:dhw.temp_d_actual_dhw, cmd:dhw.temp_d_actual_dhw, dst:15, refresh:300” }
Number e_DHW_Temp_Set “DHW Setpoin temperature [%.1f °C]” { ebus=“id:dhw.temp_d_dhw, cmd:dhw.temp_d_dhw, dst:15, refresh:300, set:dhw.set_temp_d_dhw.temp_d_dhw” }
Number e_HC1_Temp_Napis “HC1 Manual over spoint [%.1f °C]” {ebus=“id:heating.temp_d_room_override, cmd:heating.temp_d_room_override, dst:15, refresh:300” }
Number e_HC1_Temp_Set_Night “HC1 Night Setpoint [%.1f °C]” {ebus=“id:heating.temp_d_night, cmd:heating.temp_d_night, dst:15, refresh:300, set:heating.set_temp_d_night.temp_d_night”}
Number e_HC1_curve “HC1 Heating curve[%.1f]” (Vaillant) {ebus=“id:heating.temp_hcurve, cmd:heating.temp_hcurve , dst:15, refresh:300”}
Number e_HC1_Day_Temp “HC1 day temp [%.f°C]” (Vaillant) {ebus=“id:heating.temp_d_man, cmd:heating.temp_d_man, refresh:300, dst:15, set:heating.set_temp_d_man.temp_d_man”}

Items are corresponding to vaillant-vrc430-configuration.json

I also add
ebus:parserUrl=platform:/base/…/configurations/ebus-config.json
ebus:parsers=custom

(ebus-config.json is renamed vaillant-vrc430-configuration.json file from nikoraes post)

generally I can read data from listed items but can’t set any value…

Any idea how to solve problem ?
Maybe I do something wrong.
The strange is that in old version of ebus binding
some item works only with “program” at the end of set command but another need full entry. For examples
Number e_HC1_Program “Heating program HC1[%s]” (Vaillant){ ebus=“id:heating.heating_circuit_program, cmd:heating.heating_circuit_program, dst:15, refresh:300, set:heating.set_hea
ting_circuit_program.program” }
Number e_HC1_Temp_Set_Night “HC1 Night Setpoint [%.1f °C]” (Vaillant) {ebus=“id:heating.temp_d_night, cmd:heating.temp_d_night, dst:15, refresh:300, set:heating.set_temp_d_night.temp_d_night”}

I can’t explain this …
Reards
Tomek

Hello @bajan
Try to swape the wires (ebus <—> coupler)
Ebus has no polarization but sometimes it matters
Regards
Tomek

1 Like

@Tomek thnks for the hint but this is not the solution. I look further today by disconecting all Ebus devices

Hello All,

I’m so sorry, my last change to the internal configuration was not correct, so the composing of the setter telegrams stopped working. I will fix it now.

:open_mouth:

Great :smile:

Here the fixed version:

Download
org.openhab.binding.ebus-1.8.0-SNAPSHOT-RC7.jar

This version also contains the new and modified configurations from @nikoraes

Btw: I will update the wiki page today, because the cmd property is not nessary anymore in the item.configuration. So you can shorten your properties to id, set and refresh.

Hello @bajan,

as @nikoraes already mentioned, your byte date looks not correct. And that is the reason why you get all these “invalid crc” messages. More or less all your telegrams are invalid. All you telegrams are very long, so I thing you have not enought sync bytes (0xAA).

I suggest to use a terminal program like “Realterm” and adjust the input signal first. You should get a lot of 0xAA values.

I attached settings for Realterm that helps to analyse the binary eBus data.

Great job!
Setting of program and temperatures are working great, but still there is some issue with heating curve. New value is updated by old one.
I’m wondering if you have the same observation.

Hello All
Many thanks for @csowada for great works.

Ps
I have the same issue with heating curve but is minor issue for me. (Heating curve is rarely changed )

Great piece of work.
I´m following the work connecting to eBUS for two years now in various forums and have seen how much work, time and patience it takes to figure out how things work here.

Unfortunatly I do now have a Vaillant heating, but a Junkers Cerapur Aero .

Any chance to connect this ? As I´m not really into eletronics but more a software guy I´d prefer to use e.g. a pre-build eBUS interface via ethernet while openhab is running on a Pi2 on the network . Anyone running a comparable setup ? Which interfaces are you using ?

Again: :+1: for this binding.

Cheers,
Babbe

I googled for your device and it uses a different bus system. Not complete different but not compatible with this binding.
Sorry, I can’t help here.

Thnks @csowada !! But even with this software it is impossible to adjust for correct data.
I unmounted all my extra devices, changed the usb serial converter, changed the nullmodem cable, tryed on linux and Windows, googled like a freak but nothing found. And also installes latest binding from above

Maybe it is the adapter so I ordered a new one directly on USB
http://www.eservice-online.de/produkte/ebus/135/ebus-koppler-usb

If that doesn 't work I really get crazy :cry:

This is the best I can get:

A
AA BA
AA
AA BA
AA BE EA AB BB BE
AA EB
AA AF
AA EA AE
AA
AA AB
AA AF 66 FF 44 31 0D D5 22 8D 33 84 31 03 1E CA 10
AA
AA AE FA
AA BA 37 B5 09 07 4D 24 20 0D 7A E0 5C 20 2C 55 90 AE
AA 10 26 B5 04 01 01 8F FC 09 3E 85 20 21 22 85 00 01 00 E5 00 FA EE
AA AE BF 14 50 B5 0C C1 01 02 09 35 01 01 04 05 81 00 11 20 0D 22 FD
AA FA AE D5 BA
AA BB 10 65 B5 04 01 01 3A E4 19 72 01 00 00 08 13 44 85 08 6C 20 AE
AA BB AE EA
AA
AA
AA EA FA
AA BE
AA BE BF EB FA
AA 10 FE B5 05 04 27 88 33 22 F3
AA AF BA
AA
AA 10 25 B5 85 65 17 E4 02 45 21 DA 40 AB
AA
AA AF AF
AA BA EA
AA AE EA
AA FF BB AE EE
AA BA 16 27 B5 04 11 01 D9 04 0A 13 41 31 21 3D 12 02 15 31 48 F1 09
AA BA
AA BA AB 12 26 B5 05 8C 2D 4E 40 00 06 9C 90 F0 FD
AA D5
AA AB AF EA
AA FB
AA
AA EA BE
AA
AA
AA
AA
AA
AA EA
AA AE
AA
AA FA
AA
AA 14 26 B5 05 D2 65 8C 49 F0 A1 E2 00 8A 78 40 C2 FD AE BB
AA BB EA
AA
AA
AA
AA
AA
AA
AA EF
AA FB
AA AE
AA
AA
AA
AA
AA BE BA AE EA
AA
AA EF BE
AA
AA AF
AA FB BA
AA
AA
AA BB EF BA FA
AA
AA 12 3F 05 85 05 ED 81 79 3D 66 00 1C 80 F5
AA
AA
AA BE
AA
AA
AA EA 10 3F B5 89 04 1E 7D 04 10 DA 80 FE BA
AA EA
AA EA
AA
AA EA
AA
AA
AA
AA
AA
AA
AA
AA
AA
AA
AA BA
AA EB
AA BB
AA FA
AA
AA
AA AB
AA EA BA
AA
AA
AA EB AE
AA 50 52 B5 8E 0D 2D FB 11 05 10 30 EA 01 15 A0 42 AE
AA
AA
AA BB
AA
AA
AA D5 30 27 B5 8B 07 0D 04 40 BF 02 0B 2D 23 20 47 62 FA
AA
AA BF
AA
AA
AA
AA
AA EA AE EA
AA BB
AA
AA AB
AA
AA
AA
AA
AA
AA
AA
AA
AA
AA AB
AA
AA
AA
AA
AA
AA
AA
AA EA FE
AA AE EA
AA BF AE 10 5C B5 05 04 BF 10 00 C2 33 23 00 40 FD EA AE EA FE
AA
AA
AA
AA EE
AA
AA AB EA
AA BA
AA BE
AA
AA FF
AA
AA BE
AA EA FA
AA AB AE
AA
AA EB
AA
AA
AA
AA EB EA AE EA
AA BE AE 14 FE B5 05 84 27 22 37 00 78 BB BA EE BA BF
AA 50 A5 B7 14 01 17 C4 00 81 01 9A 26 BA
AA EE
AA AF
AA EA
AA EB
AA
AA
AA
AA AE
AA BA
AA BE
AA B

Maybe to order a new adapter is the best solution. You data looks not very good. To many invalid and too short telegrams.

Happy new year.

A few days ago I did a fresh install and I updated the binding to RC7 instead of RC5. I removed the cmd part of the items and the items refresh so that works. However the changing an item doesn’t seem to work anymore. Is it possible that there is a new bug in the set part?