Closed fupe closed 4 years ago
Hi @fupe , although I have tested it the latest version 2.0 should support reading and writing to your RC200 as it uses the same telegram set as the RC100 and RC300. Version 2.0 is still in development, but pretty stable. You can either download, build and upload yourself or grab the pre-built binary. Note however that it's not yet backward compatible with 1.9.x yet so you will need to re-enter all your settings (wifi, mqtt, etc) manually via the web or the new telnet console. You'll find all the info at https://github.com/proddy/EMS-ESP/blob/v2/README.md
Hi Proddy, thanks for reply. I download and setup v2.0.0b10 NOw i can see all three devices in web and putty terminal in tx_mode 1 (I try mode 1 2 3) Boiler Buderus GBx72/Trendline/Cerapur/Greenstar Si/27i 0x08 123 06.08 Controller BC25 0x09 125 03.03 Thermostat RC200/CW100 0x18 157 41.08
ems-esp:/$ show devices These EMS devices are currently active:
Boiler: Buderus GBx72/Trendline/Cerapur/Greenstar Si/27i (DeviceID:0x08 ProductID:123, Version:06.08) This Boiler will respond to telegram type IDs: 0x10 0x11 0x18 0x19 0x34 0x1C 0x2A 0x33 0x14 0x35 0x15 0x16 0x1A 0xD1 0xE3 0xE4 0xE5 0xE9 Subscribed MQTT topics: ems-esp/boiler_cmd ems-esp/boiler_cmd_wwactivated ems-esp/boiler_cmd_wwonetime ems-esp/boiler_cmd_wwcirculation ems-esp/boiler_cmd_wwtemp
Thermostat: RC200/CW100 (DeviceID:0x18, ProductID:157, Version:41.08) This Thermostat will respond to telegram type IDs: 0xA3 0x06 0x2A5 0x2B9 0x2A6 0x2BA 0x2A7 0x2BB 0x2A8 0x2BC 0x31D 0x31E
Controller: BC25 (DeviceID:0x09, ProductID:125, Version:03.03)
But, I can switch to set thermostat. ems-esp:/$ thermostat Command not found
boiler is ok
ems-esp:/$ boiler ems-esp:/boiler$
on mqtt explorer i can see boiler_data but not thermostat data. [image: image.png]
here is part of log 000+00:21:49.699 N 398: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorFast(0x18), data: 05 02 27 00 00 00 00 00 40 80 00 02 14 80 00 00 00 FF 30 48 00 CB 00 00 00 000+00:21:49.699 D 399: [emsdevice] Received UBAMonitorFast 000+00:21:49.994 N 400: [emsesp] Boiler(0x08) -> All(0x00), MC10Status(0x2A), data: 00 00 00 00 00 00 00 00 CF 00 00 80 00 00 80 00 80 00 80 00 04 000+00:21:49.994 D 401: [emsdevice] Received MC10Status 000+00:21:50.239 N 402: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 0A 02 14 02 14 00 00 00 03 00 00 57 6D 00 04 C0 00 80 00 000+00:21:50.239 D 403: [emsdevice] Received UBAMonitorWW 000+00:21:50.343 D 404: [mqtt] Publishing topic ems-esp/boiler_data (#166, attempt #1, pid 1) 000+00:21:59.673 N 405: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 0A 02 14 02 14 00 00 00 03 00 00 57 6D 00 04 C0 00 80 00 000+00:21:59.673 D 406: [emsdevice] Received UBAMonitorWW 000+00:21:59.955 N 407: [emsesp] Boiler(0x08) -> All(0x00), UBADevices(0x07), data: 0B 00 01 00 00 00 00 00 00 00 00 00 00 000+00:22:00.024 D 408: [emsdevice] Fetching values for device ID 0x08 000+00:22:00.024 D 409: [telegram] Tx read request to device 0x08 for type ID 0x19 000+00:22:00.024 D 410: [telegram] Tx read request to device 0x08 for type ID 0x33 000+00:22:00.024 D 411: [telegram] Tx read request to device 0x08 for type ID 0x16 000+00:22:00.024 D 412: [emsdevice] Fetching values for device ID 0x09 000+00:22:00.024 D 413: [emsdevice] Fetching values for device ID 0x18 000+00:22:00.024 D 414: [telegram] Tx read request to device 0x18 for type ID 0x06 000+00:22:00.201 N 415: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorFast(0x18), data: 05 02 27 00 00 00 00 00 40 80 00 02 14 80 00 00 00 FF 30 48 00 CB 00 00 00 000+00:22:00.201 D 416: [emsdevice] Received UBAMonitorFast 000+00:22:00.213 D 417: [mqtt] Publishing topic ems-esp/boiler_data (#167, attempt #1, pid 1) 000+00:22:00.444 D 418: [telegram] Sending read Tx [#101], telegram: 0B 88 19 00 20 D0 000+00:22:00.535 D 419: [emsesp] Last Tx read successful 000+00:22:00.535 N 420: [emsesp] Boiler(0x08) -> Me(0x0B), UBAMonitorSlow(0x19), data: 80 00 80 00 80 00 00 00 00 00 00 0F C7 01 74 A9 00 00 00 01 1D 3C 00 0B 07 80 17 000+00:22:00.535 D 421: [emsdevice] Received UBAMonitorSlow 000+00:22:00.583 N 422: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorSlow(0x19), data: 80 00 80 00 80 00 00 00 00 00 00 0F C7 01 74 A9 00 00 00 01 1D 3C 00 0B 07 80 6C 000+00:22:00.583 D 423: [emsdevice] Received UBAMonitorSlow 000+00:22:00.843 N 424: [emsesp] Boiler(0x08) -> All(0x00), UBAMaintenanceStatus(0x1C), data: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000+00:22:00.843 D 425: [emsdevice] Received UBAMaintenanceStatus 000+00:22:01.045 N 426: [emsesp] Boiler(0x08) -> All(0x00), MC10Status(0x2A), data: 00 00 00 00 00 00 00 00 CF 00 00 80 00 00 80 00 80 00 80 00 04 000+00:22:01.045 D 427: [emsdevice] Received MC10Status 000+00:22:01.218 D 428: [mqtt] Publishing topic ems-esp/heartbeat (#168, attempt #1, pid 1) 000+00:22:01.416 D 429: [telegram] Sending read Tx [#102], telegram: 0B 88 33 00 20 78 000+00:22:01.493 D 430: [emsesp] Last Tx read successful 000+00:22:01.493 N 431: [emsesp] Boiler(0x08) -> Me(0x0B), UBAParameterWW(0x33), data: 08 FF 3C FB 00 28 00 02 46 00 FF FF 00 000+00:22:01.493 D 432: [emsdevice] Received UBAParameterWW 000+00:22:01.766 D 433: [telegram] Sending read Tx [#103], telegram: 0B 88 16 00 20 EC 000+00:22:01.857 D 434: [emsesp] Last Tx read successful 000+00:22:01.857 N 435: [emsesp] Boiler(0x08) -> Me(0x0B), UBAParameters(0x16), data: FF 44 64 00 06 FA 0A 01 02 64 0A 00 00 00 00 00 00 00 00 00 00 00 00 00 28 00 7F 000+00:22:01.857 D 436: [emsdevice] Received UBAParameters 000+00:22:02.191 D 437: [telegram] Sending read Tx [#104], telegram: 0B 98 06 00 20 2C 000+00:22:02.267 D 438: [emsesp] Last Tx read successful 000+00:22:02.267 N 439: [emsesp] Thermostat(0x18) -> Me(0x0B), RCTime(0x06), data: 14 07 0C 1F 15 1A 04 01 18 FF 00 000+00:22:02.267 D 440: [emsdevice] Received RCTime 000+00:22:04.877 N 441: [emsesp] Thermostat(0x18) -> All(0x00), RC300Set(0x2B9), data: 1C 12 @offset 8 000+00:22:04.877 D 442: [emsdevice] Received RC300Set 000+00:22:07.130 N 443: [emsesp] Thermostat(0x18) -> All(0x00), RC300Monitor(0x2A5), data: 1C 00 00 1C A7 @offset 3 000+00:22:07.130 D 444: [emsdevice] Received RC300Monitor 000+00:22:09.668 N 445: [emsesp] Boiler(0x08) -> All(0x00), MC10Status(0x2A), data: 00 00 00 00 00 00 00 00 CF 00 00 80 00 00 80 00 80 00 80 00 04 000+00:22:09.668 D 446: [emsdevice] Received MC10Status 000+00:22:10.003 N 447: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 0A 02 14 02 14 00 00 00 03 00 00 57 6D 00 04 C0 00 80 00 000+00:22:10.003 D 448: [emsdevice] Received UBAMonitorWW 000+00:22:10.221 N 449: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorFast(0x18), data: 05 02 27 00 00 00 00 00 40 80 00 02 14 80 00 00 00 FF 30 48 00 CB 00 00 00 000+00:22:10.221 D 450: [emsdevice] Received UBAMonitorFast 000+00:22:10.286 D 451: [mqtt] Publishing topic ems-esp/boiler_data (#169, attempt #1, pid 1) 000+00:22:14.753 N 452: [emsesp] Thermostat(0x18) -> All(0x00), RCTime(0x06), data: 14 07 0C 1F 15 27 04 01 18 FF 00 000+00:22:14.753 D 453: [emsdevice] Received RCTime 000+00:22:16.925 N 454: [emsesp] Thermostat(0x18) -> Boiler(0x08), UBAFlags(0x35), data: 01 01 000+00:22:19.592 N 455: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorFast(0x18), data: 05 02 27 00 00 00 00 00 40 80 00 02 14 80 00 00 00 FF 30 48 00 CB 00 00 00 000+00:22:19.592 D 456: [emsdevice] Received UBAMonitorFast 000+00:22:19.950 N 457: [emsesp] Boiler(0x08) -> All(0x00), MC10Status(0x2A), data: 00 00 00 00 00 00 00 00 CF 00 00 80 00 00 80 00 80 00 80 00 04 000+00:22:19.950 D 458: [emsdevice] Received MC10Status 000+00:22:20.157 N 459: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 0A 02 14 02 14 00 00 00 03 00 00 57 6D 00 04 C0 00 80 00 000+00:22:20.157 D 460: [emsdevice] Received UBAMonitorWW 000+00:22:20.355 D 461: [mqtt] Publishing topic ems-esp/boiler_data (#170, attempt #1, pid 1) 000+00:22:24.703 N 462: [emsesp] Thermostat(0x18) -> Boiler(0x08), UBASetPoints(0x1A), data: 00 00 00 000+00:22:24.831 N 463: [emsesp] Thermostat(0x18) -> All(0x00), RC300Monitor(0x2A5), data: 00 FA 21 1C 00 00 1C 2C 00 63 01 01 03 00 63 01 41 00 00 11 01 04 6E 000+00:22:24.831 D 464: [emsdevice] Received RC300Monitor 000+00:22:25.073 N 465: [emsesp] Thermostat(0x18) -> All(0x00), RC300Monitor(0x2A5), data: 09 C4 00 00 07 00 00 00 00 00 00 4B 00 3C 01 FF 00 02 4B @offset 22 000+00:22:25.073 D 466: [emsdevice] Received RC300Monitor 000+00:22:25.632 N 467: [emsesp] Thermostat(0x18) -> All(0x00), RC300WWmode(0x31D), data: 00 00 08 07 8F 000+00:22:25.632 D 468: [emsdevice] Received RC300WWmode 000+00:22:25.824 N 469: [emsesp] Thermostat(0x18) -> Boiler(0x08), ?(0x23), data: 00 00 00 000+00:22:29.604 N 470: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 0A 02 14 02 14 00 00 00 03 00 00 57 6D 00 04 C0 00 80 00 000+00:22:29.604 D 471: [emsdevice] Received UBAMonitorWW 000+00:22:29.836 N 472: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorFast(0x18), data: 05 02 26 00 00 00 00 00 40 80 00 02 14 80 00 00 00 FF 30 48 00 CB 00 00 00 000+00:22:29.836 D 473: [emsdevice] Received UBAMonitorFast 000+00:22:30.094 N 474: [emsesp] Boiler(0x08) -> All(0x00), MC10Status(0x2A), data: 00 00 00 00 00 00 00 00 CF 00 00 80 00 00 80 00 80 00 80 00 04 000+00:22:30.094 D 475: [emsdevice] Received MC10Status 000+00:22:30.210 D 476: [mqtt] Publishing topic ems-esp/boiler_data (#171, attempt #1, pid 1) 000+00:22:37.254 N 477: [emsesp] Thermostat(0x18) -> All(0x00), RC300Monitor(0x2A5), data: 01 42 5C @offset 15 000+00:22:37.254 D 478: [emsdevice] Received RC300Monitor 000+00:22:37.448 N 479: [emsesp] Thermostat(0x18) -> All(0x00), RC300Monitor(0x2A5), data: 00 62 5E @offset 13 000+00:22:37.448 D 480: [emsdevice] Received RC300Monitor 000+00:22:39.542 N 481: [emsesp] Boiler(0x08) -> All(0x00), MC10Status(0x2A), data: 00 00 00 00 00 00 00 00 CF 00 00 80 00 00 80 00 80 00 80 00 04 000+00:22:39.542 D 482: [emsdevice] Received MC10Status 000+00:22:39.897 N 483: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 0A 02 14 02 14 00 00 00 03 00 00 57 6D 00 04 C0 00 80 00 000+00:22:39.897 D 484: [emsdevice] Received UBAMonitorWW 000+00:22:40.129 N 485: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorFast(0x18), data: 05 02 26 00 00 00 00 00 40 80 00 02 14 80 00 00 00 FF 30 48 00 CB 00 00 00 000+00:22:40.129 D 486: [emsdevice] Received UBAMonitorFast 000+00:22:40.267 D 487: [mqtt] Publishing topic ems-esp/boiler_data (#172, attempt #1, pid 1) 000+00:22:49.566 N 488: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorFast(0x18), data: 05 02 26 00 00 00 00 00 40 80 00 02 14 80 00 00 00 FF 30 48 00 CB 00 00 00 000+00:22:49.566 D 489: [emsdevice] Received UBAMonitorFast 000+00:22:49.807 N 490: [emsesp] Boiler(0x08) -> All(0x00), MC10Status(0x2A), data: 00 00 00 00 00 00 00 00 CF 00 00 80 00 00 80 00 80 00 80 00 04 000+00:22:49.807 D 491: [emsdevice] Received MC10Status 000+00:22:50.016 N 492: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 0A 02 14 02 14 00 00 00 03 00 00 57 6D 00 04 C0 00 80 00 000+00:22:50.016 D 493: [emsdevice] Received UBAMonitorWW 000+00:22:50.328 D 494: [mqtt] Publishing topic ems-esp/boiler_data (#173, attempt #1, pid 1)
thanks for help. Martin
pá 31. 7. 2020 v 10:20 odesílatel Proddy notifications@github.com napsal:
Closed #434 https://github.com/proddy/EMS-ESP/issues/434.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/434#event-3607435480, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWDX6M5W5JU2KOPPVZORA3R6J5GVANCNFSM4PHCS7WQ .
great!
@proddy seems you closed to fast and fail to see that there are 2 issues left.
(now we have the case mentioned here)
Quick solution is allow all thermostats as master, not only 0x10 and 0x17. This will make the system of @fupe useable. But if someone uses more RC200 for different hc we need to have hc2 type-id matched to 0x19, hc3 typ_id to 0x1A, etc. and only the fist one of these controllers is used for DHW-settings.
oh dear, I overlooked that. I'll have a think about the options.
A possible patch for the problem with multible hc and RC200 at 0x18.. is:
emsdevices.h
to
inline uint8_t device_id(uint8_t hc = 0) const {
if (((device_id_ & 0x7F) >= 0x18) && ((device_id_ & 0x7F) <= 0x1B)) {
return ((device_id_ & 0x80) + 0x18 + hc);
}
return device_id_;
}
and add optional hc to write_command
(also in emsdevices.cpp
with call of device_id(hc)
)
void write_command(const uint16_t type_id, const uint8_t offset, uint8_t * message_data, const uint8_t message_length, const uint16_t validate_typeid, const uint8_t hc = 0);
void write_command(const uint16_t type_id, const uint8_t offset, const uint8_t value, const uint16_t validate_typeid, const uint8_t hc = 0);
void write_command(const uint16_t type_id, const uint8_t offset, const uint8_t value, const uint8_t hc = 0);
and for RC100-300 in thermostat add the hc.
Then the first of the 0x18.. thermostats is registered as master with 4 hc, the others are not writeable, but writing to a hc will automatically address the right controller.
that would work. I'll add it to the new branch.
Hi proddy, I am now 1000km from home. I will return on sunday and test your path and report. Thanks Martin.
Dne po 3. 8. 2020 9:29 uživatel Proddy notifications@github.com napsal:
that would work. I'll add it to the new branch.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/434#issuecomment-667857210, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWDX6K2RKU7YABTKEAQQLLR6ZRNHANCNFSM4PHCS7WQ .
Hi proddy many thanks. now i am able to write mode and temp to thermostat. that is great. Martin
út 4. 8. 2020 v 8:21 odesílatel Martin Kaplan fupeama@gmail.com napsal:
Hi proddy, I am now 1000km from home. I will return on sunday and test your path and report. Thanks Martin.
Dne po 3. 8. 2020 9:29 uživatel Proddy notifications@github.com napsal:
that would work. I'll add it to the new branch.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/proddy/EMS-ESP/issues/434#issuecomment-667857210, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAWDX6K2RKU7YABTKEAQQLLR6ZRNHANCNFSM4PHCS7WQ .
Hi, is it possible add write temperature to Buderus rc200 thermostat? my configuration EMS-ESP version 1.9.6b0
These 3 were recognized by EMS-ESP: Boiler: Buderus GBx72/Nefit Trendline/Junkers Cerapur/Worcester Greenstar Si/27i (DeviceID: 0x08, ProductID: 123, Version: 06.08) Controller: BC25 Base Controller (DeviceID: 0x09, ProductID: 125, Version: 03.03) Thermostat: Buderus RC200/Bosch CW100/Junkers CW100 (DeviceID: 0x18, ProductID: 157, Version: 41.08)
and part of log
thanks Martin