I connected the eBus coupler to the eBus connectors of my Vaillant Ecotec
Obviously I have connectivity to my ethernet coupler
and I configured my Openhab in the following way:
It seems I made a bad assumption about my thermostat. It is not a VRC470, but a VRC470f (wireless weather dependent thermostat).
I’ll need to check if the eBus connection is correct.
Will the parser work as well?
I added a couple more items:
Number cv_controller_temp_room_status "Room temperature status [%.1f]" (CV) { ebus="id:controller.temp_room.status, refresh:10"}
Number cv_controller_status_global "System Status [%.1f]" (CV) { ebus="id:controller.status_global_system_off, refresh:10" }
Number cv_controller_room_temp "Temperature room [%.1f °C]" (CV) { ebus="id:controller.temp_room_disp, refresh:10"}
And this is the results in the logs:
2016-09-12 11:46:03.654 [DEBUG] [e.i.EBusGenericBindingProvider:88 ]- Process binding cfg for cv_controller_temp_room_status with settings id:controller.temp_room.status, refresh:10 [Context:cv.items]
2016-09-12 11:46:03.654 [DEBUG] [o.b.e.i.c.EBusCommandProcessor:91 ]- Binding changed for item cv_controller_temp_room_status
2016-09-12 11:46:03.654 [DEBUG] [o.b.e.i.c.EBusCommandProcessor:131 ]- Add polling item cv_controller_temp_room_status with refresh rate 10 to scheduler ...
2016-09-12 11:46:03.654 [DEBUG] [e.i.EBusGenericBindingProvider:88 ]- Process binding cfg for cv_controller_status_global with settings id:controller.status_global_system_off, refresh:10 [Context:cv.items]
2016-09-12 11:46:03.654 [DEBUG] [o.b.e.i.c.EBusCommandProcessor:91 ]- Binding changed for item cv_controller_status_global
2016-09-12 11:46:03.654 [DEBUG] [o.b.e.i.c.EBusCommandProcessor:131 ]- Add polling item cv_controller_status_global with refresh rate 10 to scheduler ...
2016-09-12 11:46:03.654 [DEBUG] [e.i.EBusGenericBindingProvider:88 ]- Process binding cfg for cv_controller_room_temp with settings id:controller.temp_room_disp, refresh:10 [Context:cv.items]
2016-09-12 11:46:03.654 [DEBUG] [o.b.e.i.c.EBusCommandProcessor:91 ]- Binding changed for item cv_controller_room_temp
2016-09-12 11:46:03.654 [DEBUG] [o.b.e.i.c.EBusCommandProcessor:131 ]- Add polling item cv_controller_room_temp with refresh rate 10 to scheduler ...
I believe a restart of openhab also fixed some issues… It seemed my openhab instance was struggling with something (to be investigated).
I now have access to the configured items yay!
Nevertheless, are you still interested in the TRACE logs?
Which eBus coupler are you using btw and does it allow to write on the bus instead of just reading from it? (I’m also interested in adding my Vaillant heater to openHAB)
I think that most of the eBus users uses the interface from eservice-online.de . Both variants, USB and ethernet works well with the binding. But the USB device has slightly better timings. With both devices you can read and write to the bus.
Hi,
I just started to play around with my Ethernet Ebus koppler, and after the summer I can’t get it working properly again… All I get through the terminal (Hercules) is {80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{00}{00}{00}{00}{78}{F8}{F8}{78}{00}{78}{78}{78}{00}{00}{78}{00}{F8}{78}{00}{80}{00}{78}{00}{00}{80}{80}{80}{F8}{80}{80}{00}{00}{F8}{00}{F8}{00}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{00}{00}{00}{00}{78}{F8}{F8}{78}{00}{78}{80}{00}{80}{78}{00}{80}{00}{78}{00}{80}{80}{78}{80}{00}{78}{00}{00}{80}{78}{F8}{80}{00}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}{80}{78}{F8}
I’ve tried adjusting the trimmer, but it either completely stops or I can get this as a result. No AA SYNC bytes though.
Does anyone have any idea what could I do with it?
I’ve already tried restarting the boiler (Ecotec Plus+VRC470), restarting the coupler, but neither helped.
Cheers
Edited: sorry, my stupidity… the problem was the too high (9600) setting of the serial through the 1-Wire Bus Coupler setup program. Now it’s set back to 2400 and works fine. Thanks
Does anyone managed to figure out the way to make this thing work with the VRC470? I have a lot of 10 08 B5 04/10/11/16 telegrams, but I couldn’t see one which would have been decoded properly.
I only have this in the openhab.cfg
ebus:parsers=vaillant-vrc470,vaillant-bai00
If someone could make it work, I’d love to know your items both for checking temperatures and even more for setting a temperature or operating mode for the heating.
Thank you!
Hello, I am reviving this topic.
My configuration is:
2 x Vaillant Ecotec Plus heaters
1 x VR32 ebus coupler installed in the 2nd heater
1 x Calormatic 630 controller
cascade configuration via ebus (heater #1 direct connection to ebus, heater #2 via the VR32 ebus coupler)
I have the following circuits linked together via a low loss header tank:
circuit 1: 26 radiators on 4 floors
circuit 2: 800L tank Domestic Hot Water
My goal is to expose this “cascaded” ebus instance to openhab (of course in read/write mode) while preserving the functionality of the Calormatic 630 controller.
In other words, I want to implement a “remote control” function for the Calormatic 630 via openhab, not to mention, of course, other benefits from exposing this ebus to openhab (like saving statistical data such as gas consumption, pump performance, target/current flow temperature etc. in influxdb persistence, exposing time series to Grafana etc.).
Questions:
supposing I have managed to expose the ebus to openhab (ebus shared with the Calormatic 630): if I change any ebus parameters via openhab (by writing data on ebus), will the new settings be saved also in the Calormatic 630 controller? If not, then I believe there will be conflicting data circulating on the ebus (different values for the same parameters) which might cause unexpected behavior at heaters’ level.
are there any other ebus couplers (except the USB/Serial/Ethernet ebus couplers from Esera) that I could use in order to expose the “core” ebus (heater #1 + heater #2 + Calormatic 630) to openhab? I have reserved an ebus adapter v3 from here which is designed to be used with ebusd but the developer says it is not able to communicate with cascaded heaters and that I need to buy 2 pieces of their ebus adapters and “split” the configuration in 2 different ebus instances (one for each heater). However this will break the cascade configuration and also will render the Calormatic 630 useless (which I don’t want).
yay!