[eBUS 2.0] Binding - Release 2.5.1-8

Tags: #<Tag:0x00007f6171597a20> #<Tag:0x00007f6171597958>

With the eBUS binding 2.0 you can read and control a heating system with the eBUS protocol.

Requirements

  • openHAB 2.4 or newer

  • eBUS Hardware Interface

  • eBUS protocol compatible Heating System

Documentation

Pre-Release Threads

This is the previous thread about this binding. But with the release we start a new thread to make a cut.

Download

Version 2.5.1-8 from 21.06.2020

Older Versions

Downloads

Changelogs

eBUS core

eBUS configuration

none, see GitHub commits

eBUS binding

none, see GitHub commits

Sources

The binding contains

eBUS Core library

eBUS configuration library

openHab2 Binding

2 Likes

After two years of development it was now time to set the status of binding to stable. Thanks to all involved users. With the release of openHAB 2.5 I have reworked the binding in many places and adapted it for the new BND build tool.

I will use this new thread as a fresh start after the release. So if you find an old issue please report it in this topic again. I will not dig in the old thread for open issues. Sorry …

1 Like

Thanks @csowada,

works stable and well. Besides observing the “mechanics” of my gas boiler and solar thermal, I use it together with the KNX bindung, e.g., to display some values on my “MDT Glastaster II” screens in the bathrooms. Outside temperature and warm water temperature are much appreciated, especially by my wife :sunglasses:.

Thomas

1 Like

After some build issues today I found out that I’m on the wrong branch. So the binding will be versioned as 2.5.x instead of 3.0.x . But it looks like our openHAB core dev’s have not setup the repositories for 2.5.1 snapshots.

With the current version the binding is not always starting correct. A restart of openHAB can help. I’m working on it …

Hey,
as per my understanding there wont be any 2.5.1 releases as core is focusing on 3.0 now. Only in case of critical security issue. But I might be wrong.

I’m watching your binding a bit already as I own a Wolf CGB-20 with Solar heat. I dont have any eBus interface jet, and was wondering if you could recommend some hardware. OH2 is running on a server on ground floor and heating is in basement, so I have to go LAN anyway. I was focusing on the ESERA ethernet hardware but I now saw that it has known issues. I have the mains switch box in basement room next to the heating with LAN access, so I would be able to add some converter/hardware/Pi/what not there.
Would appreciate any hardware recommendation for a proper working setup.
Thanks much in advance.
Best Sebastian

Yes that is correct, but at the moment we are only able to build for 2.5.1. The core developers started now to rewrite core parts and that means unstable code for the next time. If version 3.0 is more stable I will switch to the next major release.

The problem with ethernet and wifi is the additional delay. Sending to the bus is very time critical. Just reading is not the issue. Maybe the ebusd connector is interesting, but I have also some sending issues with it. Maybe it is just a simple bug in ebusd.

Thanks for your reply @csowada,
I have to go LAN from ground floor to basement anyway, since I cant connect RS232 between the floors. So I thought instead of plugging a Pi into mains switching cupboard which then uses RS232 towards the eBus adapter, why not using an eBus adapter which already speaks TCP/IP. So I would save one hop by excluding the Pi.
From your experience using the ESERA ethernet adapter is a bad idea, right? In the first place I want to read data for now, but have to admit that I would like to prepare for sending data as well.
The eBus Adapter looks indeed interesting. I’m fine with normal soldering, but failed with the SMD soldering of one of the older boards. And due to lack of knowledge in testing the soldered board I never know if its the soldering or something else, when something isnt working. Thats why I was mainly looking for some “ready to use” hardware.
Thanks

With a Pi and a serial/USB adapter you are more flexible to run ebusd or socat etc. But yes, it is more complex than an Ethernet adapter. But I would go this way.

thank you for your new version.

after i add “eBus Bridge” in Paper UI i got this error in my log:

15:33:56.978 [WARN ] [ommand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: data
15:33:56.985 [WARN ] [ommand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: variantTime
15:33:56.993 [WARN ] [ommand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: variantDate
15:33:57.002 [ERROR] [ebus.service.parser.EBusParserService] - error!
de.csdev.ebus.command.datatypes.EBusTypeException: The decoded datetime part of datetime is null!
at de.csdev.ebus.command.datatypes.ext.EBusTypeDateTime.decodeInt(EBusTypeDateTime.java:83) ~[196:de.cs-dev.ebus.ebus-core:0.9.20.SNAPSHOT]
at de.csdev.ebus.command.datatypes.ext.EBusTypeDateTime.decodeInt(EBusTypeDateTime.java:1) ~[196:de.cs-dev.ebus.ebus-core:0.9.20.SNAPSHOT]
at de.csdev.ebus.command.datatypes.EBusAbstractType.decode(EBusAbstractType.java:106) ~[196:de.cs-dev.ebus.ebus-core:0.9.20.SNAPSHOT]
at de.csdev.ebus.command.EBusCommandUtils.decodeValueList(EBusCommandUtils.java:374) ~[196:de.cs-dev.ebus.ebus-core:0.9.20.SNAPSHOT]
at de.csdev.ebus.command.EBusCommandUtils.decodeTelegram(EBusCommandUtils.java:426) ~[196:de.cs-dev.ebus.ebus-core:0.9.20.SNAPSHOT]
at de.csdev.ebus.service.parser.EBusParserService.onTelegramReceived(EBusParserService.java:94) [196:de.cs-dev.ebus.ebus-core:0.9.20.SNAPSHOT]
at de.csdev.ebus.core.EBusControllerBase$2.run(EBusControllerBase.java:142) [196:de.cs-dev.ebus.ebus-core:0.9.20.SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:?]
at java.lang.Thread.run(Thread.java:748) [?:?]

do you know how to fix it?

It looks like an older Version, it show core version 9.20, should be 1.0.0.
Could you please provide a detailed log with the telegram that cause this issue.

@csowada,

i receive the following error after the binding update. Furthermore i have a problem with the spezial operating mode from my vailant heating system VRC 470. If i try to select one setting, it will not be accepted and switched back to nothing.
Have you an idear how can i fix this Problem?

2020-01-01 19:02:52.188 [WARN ] [mmand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: data 58 02 19 FF FF FF FF

2020-01-01 19:02:52.190 [WARN ] [mmand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: variantTime std

2020-01-01 19:02:52.192 [WARN ] [mmand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: variantDate std

2020-01-01 19:02:52.193 [WARN ] [mmand.datatypes.ext.EBusTypeDateTime] - The decoded date and/or time part of datetime is null!

i don’t have install the addon but in my log i can find ebus Links.

How can i delete the old eBus settings?

19:35:58.453 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantVRT392_39200_ActualRoomTempDesiredHc1_CurrentRoomSetpointConsideringAllBasicConditionsPassedToTheControlAlgorithms-ebus:39200:3c6f745e:39200_ActualRoomTempDesiredHc1#ActualRoomTempDesiredHc1’ has been added.

19:35:58.462 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_modulationPump_ActualPumpSpeed-ebus:bai:84971ae0:08:bai_boiler_modulation-pump#modulation-pump’ has been added.

19:35:58.473 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI00_Bai_boiler_control_getopdata_LeadWaterTemperature-ebus:bai:f436987b:bai_boiler_control_getopdata#temp-lead-water’ has been added.

19:35:58.481 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘Tueroffner-mqtt:topic:4635ef43:intercom_opener’ has been added.

19:35:58.491 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘GenericMQTTThing_MyShelly-mqtt:topic:4635ef43:MyShelly’ has been added.

19:35:58.499 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_controller_stateThermostatRT_RoomThermostatAtTerminalRT-ebus:bai:84971ae0:08:bai_controller_state-thermostat-RT#state-thermostat-RT’ has been added.

19:35:58.509 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘WaschmaschineShelly_Meter_TotalEnergy-shelly:shelly1pm:001f4b:meter#totalKWH’ has been added.

19:35:58.518 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_ReceivedTelegrams-ebus:bridge:b4ccddfe:metrics#receivedTelegrams’ has been added.

19:35:58.525 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_tempDFlowExt_TargetValueFromExternalEBusController-ebus:bai:84971ae0:08:bai_boiler_temp-d-flow-ext#temp-d-flow-ext’ has been added.

19:35:58.534 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantVRT392_39200_Hc1OPMode_OperationModeOfTheHeatingCircuit-ebus:39200:7daaf612:39200_Hc1OPMode#Hc1OPMode’ has been added.

19:35:58.544 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘Ebusb-ebus:bai:232de689:bai_boiler_temp-d-flow#temp-d-flow’ has been added.

19:35:58.553 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI00_Bai_boiler_stateGasValve_GasValveStatus-ebus:bai:40e0a10b:bai_boiler_state-gas-valve#state-gas-valve’ has been added.

19:35:58.563 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_control_setopdata_ServiceWaterTargetTemperature-ebus:bai:84971ae0:08:bai_boiler_control_setopdata#temp-d-srv-water’ has been added.

19:35:58.569 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘Temp-mqtt:topic:4635ef43:DHT’ has been added.

19:35:58.577 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSStandard_Std_controller_dValuesRc2_BoilerDesireTemperature-ebus:std:afd1eeb3:std_controller_d-values-rc2#temp-d-boiler’ has been added.

19:35:58.586 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantVRT392_39200_DisplayedRoomTemp_DisplayedRoomTemperature-ebus:39200:3c6f745e:39200_DisplayedRoomTemp#DisplayedRoomTemp’ has been added.

19:35:58.595 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_UnresolvedTelegramsRatio-ebus:bridge:f3436c51:metrics#unresolvedRatio’ has been added.

19:35:58.602 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantVRT392_39200_Hc1QuickVetoTemp_ManualOverrideSetpointOfTheHeatingCircuit-ebus:39200:7daaf612:39200_Hc1QuickVetoTemp#Hc1QuickVetoTemp’ has been added.

19:35:58.610 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_tempCylinder_MeasuredValueOfHotWaterSensor-ebus:bai:84971ae0:08:bai_boiler_temp-cylinder#temp-cylinder’ has been added.

19:35:58.621 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_ReceivedTelegrams-ebus:bridge:dfef11ef:metrics#receivedTelegrams’ has been added.

19:35:58.630 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_ReceivedTelegrams-ebus:bridge:3128153b:metrics#unresolvedRatio’ has been added.

19:35:58.639 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_stateReturnRegulation_HeatingFlowReturnRegulationChangeover-ebus:bai:84971ae0:08:bai_boiler_state-return-regulation#state-return-regulation’ has been added.

19:35:58.650 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_tempOutlet_OutletTempActualValueStatus-ebus:bai:84971ae0:08:bai_boiler_temp-outlet#status’ has been added.

19:35:58.657 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantVRC430F470F_Vrc430_controller_time_Time-ebus:vrc430:d31a217f:vrc430_controller_time#time’ has been added.

19:35:58.667 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI00_Bai_boiler_control_datetime_Status-ebus:bai:b54ef49c:bai_boiler_state-gas-valve#state-gas-valve’ has been added.

19:35:58.676 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_tempDFlow_FlowTemperatureTargetValueOrReturnTargetValue-ebus:bai:84971ae0:08:bai_boiler_temp-d-flow#temp-d-flow’ has been added.

19:35:58.685 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_control_getopdata_ServiceWaterTemperature-ebus:bai:84971ae0:08:bai_boiler_control_getopdata#temp-srv-water’ has been added.

19:35:58.695 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_tempFlow_StatusFlowTemperature-ebus:bai:84971ae0:08:bai_boiler_temp-flow#status’ has been added.

19:35:58.701 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantVRT392_39200_HolidayEndPeriod_EndDateOfHolidays-ebus:39200:7daaf612:39200_HolidayEndPeriod#HolidayEndPeriod’ has been added.

19:35:58.710 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_control_getopdata_LeadWaterReturnTemperature-ebus:bai:84971ae0:08:bai_boiler_control_getopdata#temp-return-lead-water’ has been added.

19:35:58.719 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI00_Bai_boiler_statePumpExt_StatusOfCirculatingPump-ebus:bai:07fd36a9:bai_boiler_state-pump-ext#state-circulation-pump’ has been added.

19:35:58.730 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_postrunPump_OverrunTimeOfInternalPumpForHeatingMode-ebus:bai:84971ae0:08:bai_boiler_postrun-pump#postrun-pump’ has been added.

19:35:58.739 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_UnresolvedTelegrams-ebus:bridge:b0945ca7:metrics#unresolvedTelegrams’ has been added.

19:35:58.746 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_RoundtripTime-ebus:bridge:b0945ca7:metrics#sendReceiveRoundtripTime’ has been added.

19:35:58.755 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_tempReturn_ReturnTemperature-ebus:bai:c964e6bc:08:bai_boiler_temp-return#temp-return’ has been added.

19:35:58.764 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_pressure_BoilerPressure-ebus:bai:84971ae0:08:bai_boiler_pressure#pressure’ has been added.

19:35:58.771 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘GenericMQTTThing_IR-mqtt:topic:4635ef43:IR’ has been added.

19:35:58.781 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_UnresolvedTelegramsRatio-ebus:bridge:b0945ca7:metrics#unresolvedRatio’ has been added.

19:35:58.788 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantVRT392_39200_Hc1QuickVetoActive_ManualOverrideOfTheHeatingCircuitEnabled-ebus:39200:308b663f:39200_Hc1QuickVetoActive#Hc1QuickVetoActive’ has been added.

19:35:58.799 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_FailedTelegrams-ebus:bridge:b0945ca7:metrics#failedTelegrams’ has been added.

19:35:58.809 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘Hum-mqtt:topic:4635ef43:Feuchte’ has been added.

19:35:58.816 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSStandard_Std_autoStroker_opDataBc2tcB2_ExhaustTemperatur-ebus:std:afd1eeb3:std_auto-stroker_op-data-bc2tc-b2#temp-exhaust’ has been added.

19:35:58.823 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSStandard08_Std_controller_opDataRc2bc_StatusHeatRequest1-ebus:std:b0945ca7:08:std_controller_op-data-rc2bc#status-heat-req1’ has been added.

19:35:58.832 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_statePumpExt_StatusOfCirculatingPump-ebus:bai:84971ae0:08:bai_boiler_state-pump-ext#state-circulation-pump’ has been added.

19:35:58.841 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI0008_Bai_boiler_levelPartLoad_HeatingPartialLoad-ebus:bai:84971ae0:08:bai_boiler_level-part-load#level-part-load’ has been added.

19:35:58.851 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI00_Bai_boiler_tempDFlowExt_TargetValueFromExternalEBusController-ebus:bai:f436987b:bai_boiler_temp-d-flow-ext#temp-d-flow-ext’ has been added.

19:35:58.862 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘EBUSBridge_Metrics_ReceivedTelegrams-ebus:bridge:3128153b:metrics#failedTelegrams’ has been added.

19:35:58.873 [INFO ] [thome.event.ItemChannelLinkAddedEvent] - Link ‘VaillantBAI00_Bai_boiler_tempDFlow_FlowTemperatureTargetValueOrReturnTargetValue-ebus:bai:f436987b:bai_boiler_temp-d-flow#temp-d-flow’ has been added.

So you have remove the kar file from the addons folder? And a openhab restart? How do you define the Things ? With a text file or with Paper UI?

After i delete my config files in /var/lib/openhab2/config/org/openhab/ my log was clear of any ebus link.

Now i add your new binding in the addon folder an try to add my “Vaillant VRT 392” after adding file:///etc/openhab2/configurations/vaillant/vaillant_template.json and file:///etc/openhab2/configurations/vaillant/39200.15.392_configuration.json config url i got the same problem again:

20:05:14.764 [WARN ] [ommand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: data 37 10 06 FF FF FF FF

20:05:14.773 [WARN ] [ommand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: variantTime std

20:05:14.781 [WARN ] [ommand.datatypes.ext.EBusTypeDateTime] - DateTime Debug: variantDate std

20:05:14.790 [WARN ] [ommand.datatypes.ext.EBusTypeDateTime] - The decoded date and/or time part of datetime is null!

Here is a log of my ERRORs

14:02:14.107 [INFO ] [ome.event.ThingStatusInfoChangedEvent] - ‘ebus:bridge:8800f832’ changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
14:02:14.226 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template for id vaillant.templ.vti! (Url: bundleresource://205.fwk21558888/commands/vaillant-vrc-configuration.json)
14:02:14.323 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.unknown4! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vrc700-general-configuration.json)
14:02:14.373 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.unknown4! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vrc700-hwc-configuration.json)
14:02:14.405 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.unknown4! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vrc700-hc1-configuration.json)
14:02:14.441 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.unknown4! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vrc700-hc2-configuration.json)
14:02:14.490 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.unknown4! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vrc700-zone1-configuration.json)
14:02:14.541 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.hfrom! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vrc700-zone2-configuration.json)
14:02:14.605 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.unknown1! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vrc700-vac-configuration.json)
14:02:14.640 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.temp_sensor! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-pmw-configuration.json)
14:02:14.667 [ERROR] [.ebus.cfg.std.EBusConfigurationReader] - Unable to find a template-block with id vaillant.temp_sensor! (Url: bundleresource://205.fwk21558888/commands/vaillant/vaillant-vr90-configuration.json)
14:02:14.676 [INFO ] [.internal.things.EBusTypeProviderImpl] - Load custom configuration file ‘file:///etc/openhab2/configurations/vaillant/vaillant_template.json’ …
14:02:14.686 [ERROR] [org.apache.felix.configadmin ] - [org.openhab.binding.ebus.internal.things.EBusTypeProvider, org.eclipse.smarthome.core.thing.binding.ThingTypeProvider, org.eclipse.smarthome.core.thing.type.ChannelTypeProvider, org.eclipse.smarthome.core.thing.type.ChannelGroupTypeProvider, org.osgi.service.cm.ManagedService, id=423, unregistered]: Unexpected problem updating configuration binding.ebus
java.lang.NullPointerException: null
at org.openhab.binding.ebus.internal.things.EBusTypeProviderImpl.updateConfiguration(EBusTypeProviderImpl.java:514) ~[?:?]
at org.openhab.binding.ebus.internal.things.EBusTypeProviderImpl.updated(EBusTypeProviderImpl.java:527) ~[?:?]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189) ~[bundleFile:?]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152) [bundleFile:?]
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85) [bundleFile:?]
at org.apache.felix.cm.impl.ConfigurationManager$UpdateConfiguration.run(ConfigurationManager.java:1405) [bundleFile:?]
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138) [bundleFile:?]
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105) [bundleFile:?]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]

Okay, I’ve check the datetime issue. It looks like that the the date time broadcast from the Controller causes this every n seconds/minutes ?! I will check this tomorrow.

@csowada I think so yes every few minutes for me.
I have what i think is the same error. I am not at home at the moment so cant get to the logs easily but i’ll get a copy of the logs later and post them here.

@csowada I get this message regularly in my logs connected to a Vaillant boiler with this connected to ebusd over a network connection.

2020-01-02 20:26:14.380 [WARN ] [s.internal.handler.EBusBridgeHandler] - Resolve error 'A valid day must be in a range between 1-31 !' in Controller date from Vaillant VRC 430(f)/470(f) [data:31 08 B5 09 03 0D 61 00 2A 00 02 00 00 2C 00 AA]
2020-01-02 20:26:14.380 [ERROR] [bus.service.parser.EBusParserService] - error!
de.csdev.ebus.command.datatypes.EBusTypeException: A valid day must be in a range between 1-31 !
	at de.csdev.ebus.command.datatypes.ext.EBusTypeDate.decodeInt(EBusTypeDate.java:124) ~[bundleFile:?]
	at de.csdev.ebus.command.datatypes.ext.EBusTypeDate.decodeInt(EBusTypeDate.java:30) ~[bundleFile:?]
	at de.csdev.ebus.command.datatypes.EBusAbstractType.decode(EBusAbstractType.java:106) ~[bundleFile:?]
	at de.csdev.ebus.command.EBusCommandUtils.decodeValueList(EBusCommandUtils.java:409) ~[bundleFile:?]
	at de.csdev.ebus.command.EBusCommandUtils.decodeTelegram(EBusCommandUtils.java:461) ~[bundleFile:?]
	at de.csdev.ebus.service.parser.EBusParserService.onTelegramReceived(EBusParserService.java:94) [bundleFile:?]
	at de.csdev.ebus.core.EBusControllerBase$2.run(EBusControllerBase.java:142) [bundleFile:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_181]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_181]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]

I seem to be getting this approximately every 2 minutes. But it looks different from the log from the other user.

thank you.

Do you also know why the VRT392 json file didn’t work? ebus config json

with ebusctl ri can read the data from my vrt392 and with ebusctl write -c 392 Hc1OPMode manual i can write data to my VRT.

NEW RELEASE - 2.5.1-2

Hello All,

I’ve worked the last days to harden and simplify the new release internally. It should als fix the current issues with the broadcasts. It would be fine to get feedback regarding the open issues. This release has some larger internal changes, so it is possible that there are new issues.