Support for Enviline #330
Comments
|
What I'd like to see if the telegrams are understood or not. Is there a way to translate a telegram from the command line? info: devices: Log v: |
|
So when I want to start to find the "hot tap water on/off" telegram like is done in #309, what should I do? https://emsesp.github.io/docs/#/Deciphering-EMS-Plus is not really complete here, as it assumes too many things. |
|
Looks like your boiler is using quite different EMS+ messages that I haven't seen before and thus not yet supported by EMS-ESP, e.g. 0x101, 0x201, 0x39F, 0x3A0. The data is in those somewhere so with some trial and error we should be able to deduct what is what, And then you can help build up the library and documentation in the wiki. The EMS protocols are not publically shared unfortunately so we need to decypher ourselves. I see To get this working I would start with
There is no feature to show real-time what each of the telegrams contain but could be easily added by just adding myDebug() statements to the process function calls in |
|
Thanks for assisting! Bummer it's not supported yet, but at least we got a really new boiler, hehehe. While reading through documents about EMS+, I found out that I needed to look for telegram-types, not the full telegrams. So the below is with the "old thinking", but I keep them here as LibreOffice crashed. I'll add a new reply with the statistics for the telegram types, before going into steps 3 and 4. Ok, got some statistics from UBAMAster to All in about 4.5 minutes: 27 times, regular 6x per minute:
10 times, each minute at :00 and 14-16 seconds after each minute:
once a minute, regular:
(Did this by cleaning up the logs in notepad++: removed the lines without timestamp, made sure there are delimiters everywhere, etc. Then turned into spreadsheet and did some sorting, where I added an extra delimiter for the ones without a type, among other things. Thinking of fixing this in the code to make it more easy to parse, or make a simple counter for the 10-second and 60-second telegrams). I left out the irregular ones, but kept the edited log file. |
My background is solely https://emsesp.github.io/docs/#/MC110-controller My guess: I should look at 0x038D and 0x038F to find known temperatures, to see what is the new 0xE4? |
|
The interesting ones look like E3,E4,E9 and 39F, 38D, 38F did you manage to get a reference point? like a boiler temps that we can try and find back in these telegrams? |
|
38D and 38F are fired when I change something in the temperature. In the logs you see there are multiple of these close together - I'll leave them for later. So I think that I did not do the Excel-exercise well, and these are not regular at all. Now the boiler temperature "jumped" from 50.3 to 50.2. Watched E4. There was no 50. The numbers stat where not changing all the time, none changed there. As the temperature did not change, this could take quite some time. I'm too lazy for that... So second approach, guessing it's some HEX. Then is it 50.2 (502=01F6) or 50.20 (5020=139C)? E9 was showing 01 F6. Watched the temperature for 50.0 in other logs and bingo! 50.0°C in E9: "08 00 E9 00 37 01 F4 01 E7 00 00 00 00 41 3C 00 00 00 00 00 00 00 00 00 00 00 00 37 00 00 00" 01E7=48.7 - temp outside boiler? But wait - it looks like the exact E9. I'm now confused... |
|
could be! temps are stored as signed 2-byte integers divided by 10 so 0x01F4 is indeed 50.0 what may be handy is watching a telegram, e.g. |
|
I know how to log/watch, but not where to pay attention to. :/ Temp went to 49.8, E9 changed to 01 F2. So I'm sure it's that. Context I missed: the length of the telegrams is different. There is also a short E4, but that one is from the gateway to the UBAMaster - can be ignored. Seems that there is no FAST telegram anymore. E4, E3, E9, 0x039F, 0x03A0 and 0x03A3 are sent each 10 seconds in the same order, so some kind of mega-telegram in 6 parts: and 2 hours later: Is this also with normal EMS+? Are the lengths of all these different? Is it correct, that the last three 39F, 3A0 and 3A3 are new? So let's focus on these 6? Assuming that the 0x01XX are temperatures, still a lot to decipher. What would be a good next experiment? Is there a way to watch a selection of telegram types at once? |
|
As probably I need to start from scratch, I need to make a project plan. Just need to know where I have to start from scratch and where I can build further. @proddy Do you have a publicly editable overview in i.e. Google sheets for the various infos and the telegrams? Also, do you have written down tactics per info on how to find it? And is there a way to watch multiple telegrams at the same time? Plan:
Feedback? |
|
I don't really have a plan. It typically ends up with a lot of trial and error and your approach sounds solid. When I find something I do put it up on the wiki. Most EMS+ messages are pretty consistent across devices so its just a matter of finding the patterns. A good start would be looking at how Bosch/Junkers HT3 does it. See here. |
|
Ok, I'll set it up then. I'll take the data from the code Yeah, what I understood is that "Buderus" is behind the bus for all Bosch heaters? Unfortunately I'm not able to understand that document. I don't see any telegrams I know, so I'm not sure what I can get out of this document. Can you explain what you think I can learn from it? I see the "calculation types" there. Are these also used on Bosch/Nefit? Looked to the other doc too. Norberts1's analyser is a more advanced version of the statistics-thingy I want (watching which variables change in the telegrams). Now thinking that using mqtt for sending all the telegrams would be easier. PS: I got a full time job, so will take my time for this project |
Is your feature request related to a problem? Please describe.
This is the output that the dashboard gives. I read different data from the boiler and heatpump. Thermostat seems to be correct.
Note: with the 1.95 dev-version, it does not find the "heat pump" and does not accidentally add support.
Describe the solution you'd like
I'd like to have support for this device - got a programming and Linux background. What steps should I follow? I saw #248, but would like some assistance to get started.
The text was updated successfully, but these errors were encountered: