Thanks, looks better now, however I only receive 3 results out of all the ones I use.
This is my log:
2016-11-01 17:54:18.661 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 15 B5 09 03 0D 34 00 1E 00 01 00 9B 00 AA
2016-11-01 17:54:20.172 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d67RemainingBoilerBlockTime! Check your item configuration.
2016-11-01 17:54:22.254 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:22.254 [DEBUG] [.ebus.internal.parser.Analyses] - FF 15 B5 09 03 0D 34 00 1E 00 01 00 9B 00 AA
2016-11-01 17:54:22.262 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:22.265 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:22.263 [DEBUG] [.ebus.internal.parser.Analyses] - >>> VRT 350 HC1 modulating status
2016-11-01 17:54:25.545 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:25.548 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:26.667 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:26.803 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:27.716 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 54 00 AC AA
2016-11-01 17:54:28.188 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d13CirPump! Check your item configuration.
2016-11-01 17:54:28.472 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 08 B5 09 03 0D 54 00 AC 00 00 00 00 AA
2016-11-01 17:54:28.479 [DEBUG] [.ebus.internal.parser.Analyses] - FF 08 B5 09 03 0D 54 00 AC 00 00 00 00 AA
2016-11-01 17:54:28.480 [DEBUG] [.ebus.internal.parser.Analyses] - >>> BAI00 - d.35 Position of diverter valve (combination boilers only)
2016-11-01 17:54:32.876 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:37.183 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:54:38.165 [ERROR] [i.c.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-01 17:54:39.195 [ERROR] [o.b.e.i.c.EBusCommandProcessor] - Error while running runnable ā¦
java.lang.NullPointerException: null
at org.openhab.binding.ebus.internal.parser.EBusConfigurationProvider.getCommandById(EBusConfigurationProvider.java:259) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeEBusTelegram(EBusCommandProcessor.java:170) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeSendData(EBusCommandProcessor.java:311) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor$1.run(EBusCommandProcessor.java:102) ~[na:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
2016-11-01 17:54:41.171 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d47OutsideTemperature! Check your item configuration.
2016-11-01 17:54:44.076 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 15 B5 09 03 0D 80 00 82 00 02 52 01 7A 00 AA
2016-11-01 17:54:47.685 [DEBUG] [.ebus.internal.parser.Analyses] - FF 15 B5 09 03 0D 80 00 82 00 02 52 01 7A 00 AA
2016-11-01 17:54:47.686 [DEBUG] [.ebus.internal.parser.Analyses] - >>> VRT 350 current room temperature
2016-11-01 17:54:50.688 [DEBUG] [i.c.AbstractEBusWriteConnector] - Succcesful send: FF 08 B5 09 03 0D 3F 00 2F 00 01 01 9A 00 AA
2016-11-01 17:54:55.077 [DEBUG] [.ebus.internal.parser.Analyses] - FF 08 B5 09 03 0D 3F 00 2F 00 01 01 9A 00 AA
2016-11-01 17:54:55.079 [DEBUG] [.ebus.internal.parser.Analyses] - >>> BAI00 - d.11 Status external heating pump
2016-11-01 17:54:55.087 [DEBUG] [.ebus.internal.parser.Analyses] - 03 64 B5 12 02 02 32 54 00 06 32 01 00 80 FF FF B9 00 AA
2016-11-01 17:54:55.090 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2016-11-01 17:54:55.094 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:54:58.154 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:09.471 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 17 00 52 AA
2016-11-01 17:55:09.472 [DEBUG] [.b.e.i.c.AbstractEBusConnector] - Received telegram was invalid, skip!
2016-11-01 17:55:10.386 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:12.431 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 17 00 52 AA
2016-11-01 17:55:15.514 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:15.868 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:17.297 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:22.236 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d67RemainingBoilerBlockTime! Check your item configuration.
2016-11-01 17:55:22.237 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:23.237 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:25.256 [DEBUG] [i.c.AbstractEBusWriteConnector] - Received wrong telegram: FF 08 B5 09 03 0D 17 00 52 E6
2016-11-01 17:55:26.176 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 08 B5 09 03 0D 17 00 52 AA
2016-11-01 17:55:28.169 [ERROR] [i.c.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-01 17:55:28.190 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d13CirPump! Check your item configuration.
2016-11-01 17:55:33.704 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:36.564 [DEBUG] [i.c.AbstractEBusWriteConnector] - No answer from slave for telegram: FF 15 B5 09 03 0D 4B 00 6E AA
2016-11-01 17:55:39.205 [ERROR] [o.b.e.i.c.EBusCommandProcessor] - Error while running runnable ā¦
java.lang.NullPointerException: null
at org.openhab.binding.ebus.internal.parser.EBusConfigurationProvider.getCommandById(EBusConfigurationProvider.java:259) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeEBusTelegram(EBusCommandProcessor.java:170) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor.composeSendData(EBusCommandProcessor.java:311) ~[na:na]
at org.openhab.binding.ebus.internal.connection.EBusCommandProcessor$1.run(EBusCommandProcessor.java:102) ~[na:na]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_65]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_65]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_65]
2016-11-01 17:55:39.730 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:41.173 [WARN ] [o.b.e.i.c.EBusCommandProcessor] - No data to send for item d47OutsideTemperature! Check your item configuration.
2016-11-01 17:55:42.021 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:43.021 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:43.167 [ERROR] [i.c.AbstractEBusWriteConnector] - Send queue is full! The eBUS service will reset the queue to ensure proper operation.
2016-11-01 17:55:52.018 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
2016-11-01 17:55:54.223 [DEBUG] [i.c.AbstractEBusWriteConnector] - eBus collision with SYN detected!
My 12 year old boiler has been replaced with a new one as the main heat echanger failed with the same model name (completely new PCB and burner). The controls are still the same (350) so should still respond and many still work over ebusctl, but not through openhab.