You need a terminal program that can show the raw data in hex not as characters. Under windows I use realterm …
Hello again @csowada
I connect to ebus coupler using realterm and I get
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAA1008B511010189000932309042000000AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B50401003D0A00441823FFFF9000
AAAAAAAAAA10FEB5050204000BAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B510090000375E001301019A00AAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008
B51101018909323090FF420000D300AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA1008B510090000375E1300
01019A00AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAA
Is it OK or I sholud tune signal ???
Regards
Tomek
It looks good so far. You have many many 0xAA sync bytes, that is normal. Have you adjusted the trimmer? Or is this the setting you used for the previous post?
I did not adjust the trimmer becouse I 'am far away from my home. I do it remotely. It is localed in my second home in the mountain so I will go there for the weekend. For this time I can use only ssh:)
I believe your boiler should be compatible with the bai configuration. Almost everything that’s available in the diagnose menu can be read/set.
The ebus thermostats send the desired supply temperature to the bus. I’m not sure if the boiler would just dou this is you send this message on the bus. Because the boiler checks of a ebus thermostat is present I think it won’t work.
If you want to modulate your burner without an ebus thermostat it’s probably more reliable to use the analog input.
Do you use the lastest version of the binding? I can’t find the code lines of your log in my source files.
Here you can find the latest version eBUS Pre-Release for 1.8.0
Hello all
First for all I want to thanks for yours patience 
I did a little experiment. I stopped openhab and i set up ebusd ( i copied 430.csv, bai.csv, broadcast.csv, common.csv, and scan.cv to /etc/ebusd) and i get this
015-12-14 19:16:13.023 [main notice] ebusd 1.3.0 started
2015-12-14 19:16:13.120 [main notice] found messages: 442 (0 conditional on 0 conditions, 0 poll, 13 update)
2015-12-14 19:16:13.132 [bus notice] signal acquired
2015-12-14 19:16:23.566 [bus notice] new master 10
2015-12-14 19:16:23.572 [update notice] unknown BC cmd: 10feb505020400
2015-12-14 19:16:43.502 [update notice] update broadcast vdatetime QQ=10: 19:16:28;14.12.2014
2015-12-14 19:16:53.867 [bus notice] new master 03
2015-12-14 19:16:53.868 [update notice] update heatgen Status02 QQ=10: auto;60;75.0;80;52.0
2015-12-14 19:16:55.596 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:17:01.659 [update notice] update heatgen Status01 QQ=10: 23.0;22.0;-0.438;-;32.0;ok
2015-12-14 19:17:03.604 [update notice] update broadcast outsidetemp QQ=10: -0.438
2015-12-14 19:17:21.809 [update error] unable to parse heatgen DateTime from 1008b5040100 / 0a00554000ffffffff90ff: ERR: argument value out of valid ran
ge
2015-12-14 19:17:22.029 [update notice] unknown BC cmd: 10feb505020400
2015-12-14 19:17:35.925 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:17:41.977 [update notice] update broadcast vdatetime QQ=10: 19:17:26;14.12.2014
2015-12-14 19:17:46.001 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:18:02.089 [update notice] update broadcast outsidetemp QQ=10: -0.438
2015-12-14 19:18:04.187 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:18:14.247 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:18:22.549 [update notice] unknown BC cmd: 10feb505020400
2015-12-14 19:18:24.373 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:18:40.494 [update notice] update broadcast vdatetime QQ=10: 19:18:25;14.12.2014
2015-12-14 19:18:44.511 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:18:50.559 [update error] unable to parse heatgen DateTime from 1008b5040100 / 0a00274200ffffffff90ff: ERR: argument value out of valid ran
ge
2015-12-14 19:19:00.601 [update notice] update broadcast outsidetemp QQ=10: -0.438
2015-12-14 19:19:02.660 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:19:10.722 [update notice] update heatgen Status02 QQ=10: auto;60;75.0;80;52.0
2015-12-14 19:19:12.774 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:19:18.804 [update notice] update heatgen Status01 QQ=10: 22.0;22.0;-0.438;-;32.0;ok
2015-12-14 19:19:21.034 [update notice] unknown BC cmd: 10feb505020400
2015-12-14 19:19:32.560 [update notice] update heatgen Mode QQ=10: standby
2015-12-14 19:19:40.553 [update notice] update broadcast vdatetime QQ=10: 19:19:25;14.12.2014
@csowada I will copy latest binding from your post to /opt/openhab/adds/
@nikoraes if i want to use bai configuration i should copy vaillant-bai00-configuration.json from your post to /opt/openhab/configuration/ change entries in openhab.cfg to
ebus:parserUrl=platform:/base/…/configurations/ebus-config.json
ebus:parsers=custom
Is it correct ?
The new binding already comes with some vaillant configurations that you can try. You can set it in your openhab.cfg.
Hello
I installed new version of binding, increased logging and tray change parser to bai00,vrc430 or vrc470. In all cases i get the same
12:36:17.311 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:17.312 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:21.299 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:21.300 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:23.309 [DEBUG] [.ebus.internal.parser.Analyses:267 ] - 10 08 B5 04 01 00 3D 00 0A 00 50 30 18 FF FF FF FF 40 02 C9 00 AA
12:36:23.312 [DEBUG] [.ebus.internal.parser.Analyses:277 ] - >>> Unknown ----------------------------------------
12:36:23.585 [DEBUG] [.ebus.internal.parser.Analyses:267 ] - 10 08 B5 11 01 02 8A 00 05 03 3C 96 50 68 94 00 AA
12:36:23.587 [DEBUG] [.ebus.internal.parser.Analyses:277 ] - >>> Unknown ----------------------------------------
12:36:27.342 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:27.343 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:31.346 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:31.347 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:33.296 [DEBUG] [.ebus.internal.parser.Analyses:267 ] - 10 FE B5 16 03 01 40 02 16 AA
12:36:33.299 [DEBUG] [.ebus.internal.parser.Analyses:277 ] - >>> Unknown ----------------------------------------
12:36:35.351 [DEBUG] [.ebus.internal.parser.Analyses:267 ] - 10 08 B5 10 09 00 00 33 5E FF FF 04 FF 00 D1 00 01 01 9A 00 AA
12:36:35.353 [DEBUG] [.ebus.internal.parser.Analyses:277 ] - >>> Unknown ----------------------------------------
12:36:41.346 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:41.347 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:43.329 [DEBUG] [.ebus.internal.parser.Analyses:267 ] - 10 08 B5 11 01 02 8A 00 05 03 3C 96 50 68 94 00 AA
12:36:43.332 [DEBUG] [.ebus.internal.parser.Analyses:277 ] - >>> Unknown ----------------------------------------
12:36:45.378 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:45.379 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:51.844 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:51.845 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:53.819 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:53.820 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!
12:36:54.043 [DEBUG] [.ebus.internal.parser.Analyses:267 ] - 10 FE B5 05 02 04 00 0B AA
12:36:54.045 [DEBUG] [.ebus.internal.parser.Analyses:277 ] - >>> Unknown ----------------------------------------
Hello @Tomek,
could you increase the logging to level TRACE? Then the logger should show the wrong byte telegrams.
I think this is only a bug that can be ignored. But if i know the reason i can fix it.
Hello @csowada
i turn TRACE level for
org.openhab.binding.ebus.parser.EBusTelegramParser
org.openhab.binding.ebus.internal.parser.Analyses
org.openhab.binding.ebus.internal.parser.BruteForce
and get something like that
2015-12-15 15:17:57.957 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 08 00 42 17 15 15 12 02 14 88 AA 2015-12-15 15:17:57.960 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ---------------------------------------- 2015-12-15 15:17:57.961 [TRACE] [b.e.internal.parser.BruteForce] - 10 FE B5 16 08 00 42 17 15 15 12 02 14 88 AA 2015-12-15 15:17:57.962 [TRACE] [b.e.internal.parser.BruteForce] - Pos WORD UInt DATA2B DATA2C DATA1c BCD 2015-12-15 15:17:57.963 [TRACE] [b.e.internal.parser.BruteForce] - ----------------------------------------------------------------------------- 2015-12-15 15:17:57.964 [TRACE] [b.e.internal.parser.BruteForce] - 6 16896 0 66.0 1056.0 33.0 0 2015-12-15 15:17:57.965 [TRACE] [b.e.internal.parser.BruteForce] - 7 5954 66 23.257812 372.125 11.0 42 2015-12-15 15:17:57.966 [TRACE] [b.e.internal.parser.BruteForce] - 8 5399 23 21.089844 337.4375 10.0 17 2015-12-15 15:17:57.967 [TRACE] [b.e.internal.parser.BruteForce] - 9 5397 21 21.082031 337.3125 10.0 15 2015-12-15 15:17:57.968 [TRACE] [b.e.internal.parser.BruteForce] - 10 4629 21 18.082031 289.3125 9.0 15 2015-12-15 15:17:57.969 [TRACE] [b.e.internal.parser.BruteForce] - 11 530 18 2.0703125 33.125 1.0 12 2015-12-15 15:17:57.970 [TRACE] [b.e.internal.parser.BruteForce] - 12 5122 2 20.007812 320.125 10.0 2 2015-12-15 15:17:57.971 [TRACE] [b.e.internal.parser.BruteForce] - 13 — 20 — — — 14 2015-12-15 15:17:58.210 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 12 02 00 00 CA 00 00 00 00 AA 2015-12-15 15:17:58.213 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ---------------------------------------- 2015-12-15 15:17:58.214 [TRACE] [b.e.internal.parser.BruteForce] - 10 08 B5 12 02 00 00 CA 00 00 00 00 AA 2015-12-15 15:17:58.215 [TRACE] [b.e.internal.parser.BruteForce] - Pos WORD UInt DATA2B DATA2C DATA1c BCD 2015-12-15 15:17:58.215 [TRACE] [b.e.internal.parser.BruteForce] - ----------------------------------------------------------------------------- 2015-12-15 15:17:58.216 [TRACE] [b.e.internal.parser.BruteForce] - 6 0 0 0.0 0.0 0.0 0 2015-12-15 15:17:58.217 [TRACE] [b.e.internal.parser.BruteForce] - 7 — 0 — — — 0 2015-12-15 15:17:58.218 [TRACE] [b.e.internal.parser.BruteForce] - ---------------------------------- Answer ---------------------------------- 2015-12-15 15:18:01.979 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 10 09 00 00 35 5E FF FF 04 FF 00 72 00 01 01 9A 00 AA 2015-12-15 15:18:01.983 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ---------------------------------------- 2015-12-15 15:18:01.984 [TRACE] [b.e.internal.parser.BruteForce] - 10 08 B5 10 09 00 00 35 5E FF FF 04 FF 00 72 00 01 01 9A 00 AA 2015-12-15 15:18:01.985 [TRACE] [b.e.internal.parser.BruteForce] - Pos WORD UInt DATA2B DATA2C DATA1c BCD 2015-12-15 15:18:01.986 [TRACE] [b.e.internal.parser.BruteForce] - ----------------------------------------------------------------------------- 2015-12-15 15:18:01.987 [TRACE] [b.e.internal.parser.BruteForce] - 6 0 0 0.0 0.0 0.0 0 2015-12-15 15:18:01.988 [TRACE] [b.e.internal.parser.BruteForce] - 7 13568 0 53.0 848.0 26.0 0 2015-12-15 15:18:01.990 [TRACE] [b.e.internal.parser.BruteForce] - 8 24117 53 94.20703 1507.3125 47.0 35 2015-12-15 15:18:01.991 [TRACE] [b.e.internal.parser.BruteForce] - 9 -162 94 -0.6328125 -10.125 127.0 64 2015-12-15 15:18:01.993 [TRACE] [b.e.internal.parser.BruteForce] - 10 -1 255 -0.00390625 -0.0625 127.0 5 2015-12-15 15:18:01.995 [TRACE] [b.e.internal.parser.BruteForce] - 11 1279 255 4.9960938 79.9375 2.0 5 2015-12-15 15:18:01.996 [TRACE] [b.e.internal.parser.BruteForce] - 12 -252 4 -0.984375 -15.75 127.0 4 2015-12-15 15:18:01.997 [TRACE] [b.e.internal.parser.BruteForce] - 13 255 255 0.99609375 15.9375 0.0 5 2015-12-15 15:18:01.998 [TRACE] [b.e.internal.parser.BruteForce] - 14 — 0 — — — 0 2015-12-15 15:18:01.999 [TRACE] [b.e.internal.parser.BruteForce] - ---------------------------------- Answer ---------------------------------- 2015-12-15 15:18:02.000 [TRACE] [b.e.internal.parser.BruteForce] - 6 — 1 — — — 1 2015-12-15 15:18:05.970 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 11 01 01 89 00 09 30 30 D0 01 FF 3A 00 00 FF A3 00 AA 2015-12-15 15:18:05.974 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ---------------------------------------- 2015-12-15 15:18:05.975 [TRACE] [b.e.internal.parser.BruteForce] - 10 08 B5 11 01 01 89 00 09 30 30 D0 01 FF 3A 00 00 FF A3 00 AA 2015-12-15 15:18:05.976 [TRACE] [b.e.internal.parser.BruteForce] - Pos WORD UInt DATA2B DATA2C DATA1c BCD 2015-12-15 15:18:05.977 [TRACE] [b.e.internal.parser.BruteForce] - ----------------------------------------------------------------------------- 2015-12-15 15:18:05.978 [TRACE] [b.e.internal.parser.BruteForce] - 6 — 1 — — — 1 2015-12-15 15:18:05.979 [TRACE] [b.e.internal.parser.BruteForce] - ---------------------------------- Answer ---------------------------------- 2015-12-15 15:18:05.981 [TRACE] [b.e.internal.parser.BruteForce] - 6 12336 48 48.1875 771.0 24.0 30 2015-12-15 15:18:05.984 [TRACE] [b.e.internal.parser.BruteForce] - 7 -12240 48 -47.8125 -765.0 104.0 30 2015-12-15 15:18:05.987 [TRACE] [b.e.internal.parser.BruteForce] - 8 464 208 1.8125 29.0 0.0 -30 2015-12-15 15:18:05.989 [TRACE] [b.e.internal.parser.BruteForce] - 9 -255 1 -0.99609375 -15.9375 127.0 1 2015-12-15 15:18:05.992 [TRACE] [b.e.internal.parser.BruteForce] - 10 15103 255 58.996094 943.9375 29.0 5 2015-12-15 15:18:05.995 [TRACE] [b.e.internal.parser.BruteForce] - 11 58 58 0.2265625 3.625 0.0 40 2015-12-15 15:18:05.997 [TRACE] [b.e.internal.parser.BruteForce] - 12 0 0 0.0 0.0 0.0 0 2015-12-15 15:18:06.000 [TRACE] [b.e.internal.parser.BruteForce] - 13 -256 0 -1.0 -16.0 127.0 0 2015-12-15 15:18:06.002 [TRACE] [b.e.internal.parser.BruteForce] - 14 — 255 — — — 5
Hello @Tomek,
I need the log around this message below. Should start with -> DATA: {} XX XX XX XX .....
You can reduce logging for Bruteforce, this is only useful for reverse engineering unknown telegrams.
12:36:45.378 [WARN ] [.ebus.internal.utils.EBusUtils:316 ] - Unexpect ACK value in eBUS telegram, skip data!
12:36:45.379 [DEBUG] [.b.e.i.c.AbstractEBusConnector:271 ] - Received telegram was invalid, skip!`OK
I modify the logging
Hello @csowada
I get that
2015-12-15 15:42:47.943 [INFO ] [.o.b.ebus.internal.EBusBinding] - Update eBus Binding configuration …
2015-12-15 15:42:49.167 [INFO ] [.o.b.ebus.internal.EBusBinding] - Enable CSV writer for eBUS all,debug,unknown
2015-12-15 15:42:50.643 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 08 00 35 42 15 15 12 02 14 9A AA
2015-12-15 15:42:50.650 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:42:50.882 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 12 02 00 00 CA 00 00 00 00 AA
2015-12-15 15:42:50.886 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:42:52.659 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:42:58.733 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:00.738 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:01.008 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:02.738 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:08.808 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:09.041 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 03 01 D0 01 2C AA
2015-12-15 15:43:09.044 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:43:12.851 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:16.895 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:18.884 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:22.933 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 10 09 00 00 35 5E FF FF 04 FF 00 72 00 01 01 9A 00 AA
2015-12-15 15:43:22.938 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:43:26.964 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:28.969 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:29.191 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 05 02 04 00 0B AA
2015-12-15 15:43:29.194 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:43:33.040 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:37.044 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:43.079 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:47.122 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:49.136 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 08 00 34 43 15 15 12 02 14 82 AA
2015-12-15 15:43:49.140 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:43:49.391 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 12 02 00 00 CA 00 00 00 00 AA
2015-12-15 15:43:49.394 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:43:51.138 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:57.212 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 11 01 01 89 00 09 2C 2C D0 01 FF 3A 00 00 FF 90 00 AA
2015-12-15 15:43:57.215 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:43:59.216 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:43:59.488 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:01.255 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:07.329 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:09.314 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 03 01 D0 01 2C AA
2015-12-15 15:44:09.317 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:44:11.363 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:17.436 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:19.420 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:21.475 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:25.519 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:27.487 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:27.709 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 05 02 04 00 0B AA
2015-12-15 15:44:27.711 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:44:31.562 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:35.566 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:41.635 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:45.670 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:47.682 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 08 00 32 44 15 15 12 02 14 37 AA
2015-12-15 15:44:47.685 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:44:47.940 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 12 02 00 00 CA 00 00 00 00 AA
2015-12-15 15:44:47.943 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:44:51.706 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:55.742 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 11 01 01 89 00 09 3A 2E D0 01 FF 3A 01 00 FF 9B 00 AA
2015-12-15 15:44:55.745 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:44:57.789 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:58.056 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:44:59.792 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:05.855 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:07.767 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 03 01 D0 01 2C AA
2015-12-15 15:45:07.770 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:45:09.891 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:15.891 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:17.937 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:19.924 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:26.003 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:28.009 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:28.232 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 05 02 04 00 0B AA
2015-12-15 15:45:28.234 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:45:30.049 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:34.085 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:40.115 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 10 09 00 00 35 5E FF FF 04 FF 00 72 00 01 01 9A 00 AA
2015-12-15 15:45:40.118 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:45:44.156 [WARN ] [.ebus.internal.utils.EBusUtils] - Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 15:45:46.173 [DEBUG] [.ebus.internal.parser.Analyses] - 10 FE B5 16 08 00 31 45 15 15 12 02 14 4E AA
2015-12-15 15:45:46.176 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
2015-12-15 15:45:46.425 [DEBUG] [.ebus.internal.parser.Analyses] - 10 08 B5 12 02 00 00 CA 00 00 00 00 AA
2015-12-15 15:45:46.428 [DEBUG] [.ebus.internal.parser.Analyses] - >>> Unknown ----------------------------------------
do you disabled the trace level? Please set it like below, I need the binary data from “org.openhab.binding.ebus.internal.parser.Analyses”
org.openhab.binding.ebus.internal.parser.Analyses =>> TRACE
org.openhab.binding.ebus.internal.parser.BruteForce =>> INFO@csowada
OK my fault
I get data like this
2015-12-15 19:43:52 DEBUG o.o.b.e.internal.EBusBinding[:285]- eBus binding has been started.
2015-12-15 19:43:55 INFO o.o.b.e.internal.EBusBinding[:137]- Update eBus Binding configuration …
2015-12-15 19:43:55 DEBUG o.o.b.e.internal.EBusBinding[:176]- Load eBus Parser Configuration “common” …
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:150]- Compile RegEx filter: [0-9A-Z]{2} FE 03 01 0E .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:150]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} 05 03 08 01 .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:150]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} 05 07 09 .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:150]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} 07 00 09 .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} 07 04 [0-9A-Z]{2} .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:150]- Compile RegEx filter: [0-9A-Z]{2} FE 07 04 0A .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} 07 FE [0-9A-Z]{2} .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} 07 FF [0-9A-Z]{2} .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:150]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} 08 00 .*
2015-12-15 19:43:56 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:150]- Compile RegEx filter: [0-9A-Z]{2} FE FE 01 0A .*
2015-12-15 19:43:56 INFO o.o.b.e.internal.EBusBinding[:226]- Enable CSV writer for eBUS all,debug,unknown
2015-12-15 19:43:56 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:56 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:56 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:56 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:56 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 WARN o.o.b.e.i.utils.EBusUtils[:316]- Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 19:43:57 TRACE o.o.b.e.i.utils.EBusUtils[:318]- -> DATA: 10 08 B5 10 09 00 00 35 5E FF FF 04 FF 00 72 01 01 9A 00 AA
2015-12-15 19:43:57 DEBUG o.o.b.e.i.c.AbstractEBusConnector[:271]- Received telegram was invalid, skip!
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:43:57 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:44:51 TRACE o.o.b.e.internal.EBusBinding[:362]- No valid parser result for raw telegram!
2015-12-15 19:45:22 WARN o.o.b.e.i.utils.EBusUtils[:316]- Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 19:45:22 TRACE o.o.b.e.i.utils.EBusUtils[:318]- -> DATA: 10 08 B5 04 01 00 3D 0A 00 37 52 01 FF FF FF FF D0 01 40 00 AA
2015-12-15 19:45:22 DEBUG o.o.b.e.i.c.AbstractEBusConnector[:271]- Received telegram was invalid, skip!
2015-12-15 19:45:22 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:45:22 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:45:22 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:45:22 TRACE o.o.b.e.i.c.AbstractEBusConnector[:230]- Auto-SYN byte received
2015-12-15 19:45:22 WARN o.o.b.e.i.utils.EBusUtils[:316]- Unexpect ACK value in eBUS telegram, skip data!
2015-12-15 19:45:22 TRACE o.o.b.e.i.utils.EBusUtils[:318]- -> DATA: 10 08 B5 11 01 02 8A 05 03 3C 96 50 68 94 00 AA
2015-12-15 19:45:22 DEBUG o.o.b.e.i.c.AbstractEBusConnector[:271]- Received telegram was invalid, skip!
Regards
Tomek
Hello again
I changed openhab.cfg and now I get
2015-12-16 09:25:48 DEBUG o.o.b.e.i.c.EBusCommandProcessor[:89]- Binding changed for item e_Temp_Zew
2015-12-16 09:25:48 DEBUG o.o.b.e.internal.EBusBinding[:285]- eBus binding has been started.
2015-12-16 09:25:51 INFO o.o.b.e.internal.EBusBinding[:137]- Update eBus Binding configuration …
2015-12-16 09:25:51 DEBUG o.o.b.e.internal.EBusBinding[:171]- Load custom eBus Parser with url platform:/base/…/configurations/ebus-config.json
2015-12-16 09:25:52 WARN o.a.c.DefaultAnnotationProcessor[:178]- Unable to detect annotations. Application may fail to deploy.
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 80 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 00 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 62 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 42 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0E 42 00 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 44 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0E 44 00 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 86 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 2F 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0E 2F 00 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 30 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0E 30 00 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 27 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0E 27 00 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 3C 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0D 31 00 .*
2015-12-16 09:25:52 TRACE o.o.b.e.i.p.EBusConfigurationProvider[:174]- Compile RegEx filter: [0-9A-Z]{2} [0-9A-Z]{2} B5 09 [0-9A-Z]{2} 0E 31 00 00 .*
Is it OK ?
Thank you,
I will analyse your telegrams this evening, I could see that some telegram miss the first slave byte.
@csowada
Great news !!!
Outside temp works OK !!!:
I trying to define several items
I put into my items definition HC1 operation status and DHW operation status.
It looks ok I get appropriate status but i have a little problem
Mayby it trivial but i cant get “auto” instead “2”
here is my site
Text item=e_HC1_Program label=“HC1 program [%s]”
and items definiton
Number e_HC1_Program "Heating program HC1 " { ebus=“id:heating.heating_circuit_program, cmd:heating.heating_circuit_program, dst:15, refresh:300” }
In openhab.log i get auto
That’s sound great. I released a new test version in another topic, maybe it helps with your issue.