Skip to content
This repository has been archived by the owner on Oct 4, 2021. It is now read-only.

Gather EMS Ids & Versions #18

Closed
sysrun opened this issue Dec 26, 2018 · 19 comments
Closed

Gather EMS Ids & Versions #18

sysrun opened this issue Dec 26, 2018 · 19 comments
Labels
question Further information is requested

Comments

@sysrun
Copy link

sysrun commented Dec 26, 2018

I am trying to implement my RC35 (Buderus) controller i found out that the current implementation is not able to gather the thermostat information correctly as my RC35 is using HK1 for heating.
So currently for the code is not able to distinguish between RC30 & RC35 as both use the id 0x10

I'd like to gather some more informations about the different setups.

I issued the following commands to get some more infos:

BC10:
r 0b 88 02 00 08 -> Product ID 123. Version 04.05

Original RC35:
r 0b 90 02 00 08 -> Product ID 86. Version 01.15

Maybe we can compile a list of Product IDs & Versions somehow

@sysrun sysrun added the question Further information is requested label Dec 26, 2018
@proddy
Copy link
Collaborator

proddy commented Dec 26, 2018 via email

@sysrun
Copy link
Author

sysrun commented Dec 26, 2018

Well, skills are quite good - i can understand 90% of the C code ;) Binary ops etc are no problem. So extending existing code is not really a problem (adding new ems telegrams etc.)

@SpaceTeddy
Copy link
Contributor

dear sysrun,
my Sieger BK15 with es73 (RC30 like) controller:
Sending raw telegram: 0B 88 02 00 08 (CRC=94, #data=1) (01:19:52) Corrupt telegram: telegram: 00 08 (CRC=94) (01:19:52) Boiler -> me, type 0x02 telegram: 08 0B 02 00 40 03 06 00 00 00 00 00 (CRC=DE, #data=8) (01:19:52) <--- Version(0x02) received (01:19:52) Product ID 64. Version 03.06

(01:20:27) Sending raw telegram: 0B 90 02 00 08 (CRC=54, #data=1) (01:20:27) Corrupt telegram: telegram: 00 08 (CRC=54) (01:20:27) Thermostat -> me, type 0x02 telegram: 10 0B 02 00 4C 02 08 (CRC=18, #data=3) (01:20:27) <--- Version(0x02) received (01:20:27) Product ID 76. Version 02.08

@proddy
Copy link
Collaborator

proddy commented Dec 28, 2018 via email

@SpaceTeddy
Copy link
Contributor

yes for sure, I can test it.

@sysrun
Copy link
Author

sysrun commented Jan 2, 2019

Just tried the 1.2.2 - works for me :) Awesome!
Found a Boiler compatible device, model MC10/UBA3 Boiler with TypeID 0x08, Product ID 123, Version 04.05
Found a Thermostat. Model RC35 with TypeID 0x10, Product ID 86, Version 01.15

One thing: I don't have any room sensor/thermostat (RC35 is build into the heater).
Current room temperature: 3200.0 C

@proddy
Copy link
Collaborator

proddy commented Jan 3, 2019

can you do a 't 3e' which will fetch the status message telegram from built-in thermostat, and post the results back. The room temperature should be byte 3 and 4 of the data package. If there is no sensor it should be 0x80 and 0x00.

@sysrun
Copy link
Author

sysrun commented Jan 3, 2019

Requesting type RC35StatusMessage(0x3E) from dest 0x10
(09:52:35) Sending read of type 0x3E to 0x10: telegram: 0B 90 3E 00 63 (CRC=CF), #data=1
(09:52:35) Thermostat -> me, type 0x3E telegram: 10 0B 3E 00 80 02 28 7D 00 00 00 00 00 00 00 00 64 11 3A 00 (CRC=4E), #data=16

According to EMS-Wiki its byte 8 & 9 (16Bit) and 0x7d00 is stands for "HK1 Disabled" - which is not true....

https://emswiki.thefischer.net/doku.php?id=wiki:ems:telegramme

@proddy
Copy link
Collaborator

proddy commented Jan 3, 2019

Ok, think I fixed this in my latest 1.2.3

@sysrun
Copy link
Author

sysrun commented Jan 3, 2019

Looks good now (Current room temperature: ? C)

@SpaceTeddy
Copy link
Contributor

SpaceTeddy commented Jan 5, 2019

  • two additional Product ID'd and SW Versions, because I've installed an RFM20 + RC20RF as well.

- RFM20 -> ID = 0x09 -> raw telegram: 08 89 02 00 63 (CRC=C7), #data=1 -> 0x09 -> me, type 0x02 telegram: 09 0B 02 00 44 02 03 (CRC=25), #data=3 -> Unrecognized device found. Product ID 68, Version 02.03

- RC20RF -> ID = 0x18 -> raw telegram: 0B 98 02 00 63 (CRC=7F), #data=1 -> 0x18 -> me, type 0x02 telegram: 18 0B 02 00 5D 02 00 5E 02 01 (CRC=7F), #data=6 -> Unrecognized device found. Product ID 93, Version 02.00

@proddy
Copy link
Collaborator

proddy commented Jan 5, 2019

thanks @SpaceTeddy. These will be included in the next build.

@Bonusbartus
Copy link
Contributor

The autodetect is not working for me either, since the last update (comming from 1.2.0) I cannot get any boiler information. I am using a Nefit Topline Compact HRC30 CW5 with a moduline 300 thermostat.
In the old versions, all data seemed to work perfectly.
the discovered deviceIDs are:
0x08: Unrecognized device found. Product ID 115, Version 03.06
0x09: Unrecognized device found. Product ID 114, Version 01.03

@proddy
Copy link
Collaborator

proddy commented Jan 16, 2019

That's because these devices haven't been added to the list. You'll need to manually add to ems_devices.h

For now to get it working, hard code these in my_devices.h like

#define MY_BOILER_MODELID EMS_MODEL_UBA
#define MY_THERMOSTAT_MODELID EMS_MODEL_RC20

@proddy
Copy link
Collaborator

proddy commented Jan 23, 2019

@Bonusbartus I've added these to version 1.3.2

@lobocobra
Copy link

Luckily I have no boiler attached, because the water would be quite cold :-)
=> Warm Water current temperature: -3200.0 C

Not a real isse for me, but maybe it makes sense to eliminate values <0° and higher as 110°?

@proddy
Copy link
Collaborator

proddy commented Mar 5, 2019

Good idea. But can you create a new github bug for this request and I’ll make the change. Thanks

@proddy
Copy link
Collaborator

proddy commented Mar 6, 2019

@lobocobra for the minus -3200C warm water temperature problem could do a log v boiler read 34 and post back the telegram. The code should be able to detect n/a values.

@lobocobra
Copy link

Thanks! with your latest fix the 3200C warm water temperature problem is solved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

5 participants