could Junkers FR10 get implemented? #98
Comments
|
could you build the latest build from the dev branch and do an |
|
Yeah I found it, that's why I deleted the question :) I'm trying to figure this out. It's all new to me. |
|
this is what I got: autodetect deep These 1 EMS devices were detected: If any are marked as 'unknown', please report as a GitHub issue so we can update the EMS devices database. So the junkers FR10 is not detected. Whenever I turn the knob or push the button on the thermostat I see it right away in the log. |
|
strange that it didn't find the thermostat. Can you do a You could also manually set it using |
|
finally found a bit of time to test this out. So with autodetect deep, only the boiler is detected. I manually set the thermostat type to 10 and then whenever i turn the thermostat knob or push the mode button the log reflects it: in purple: not sure if the send command delivered anything useful: I'm very tempted to order a junkers CR10 which may or may not behave similar as the rc10. |
|
We should be able to figure this out. Did you pull the latest build from yesterday? I’ve been making changes to how EMS+ is handled |
|
I think so, this was on EMS-ESP version 1.7.0b8 |
|
Hi @proddy |
|
It’s strange that the thermostat doesn’t respond to a version check with ‘send 0B 90 02 00 20’. That’s the first thing we need to solve. We could decipher the thermostat calls from the ems+ type 6F. Could you look at the temperature and at the same time record what is broadcast on the 6F and we’ll see if we can work out where the values are stored. |
|
I've been logging for a while and changing the setpoint temperature on the thermostat, nothing of type 6F is broadcast but when i turn the knob I do get following messages containing 6F, not sure if that is what you are after, though. the HEX values in bold represent the room temperature setpoint |
|
when sending ‘send 0B 90 02 00 20’ in telnet, I get no answer, not even when logging is on |
|
Seems to be a known issue with the Junkers. We're working on it! |
|
amazing, thanks! |
|
@sadrov we made some changes to the 1.7 code to better handle EMS+ messages. Can you look at the current room temperature and also the setpoint temperature on your FR10 thermostat and post back here any telegrams you see starting with |
|
I just flashed the wemos with the latest firmware version 1.7.0b14. Good news is that now the wifi password with special characters is indeed working. When I do 'info' I get the same info as before, only my boiler is not automatically recognized anymore. So I manually set boiler and thermostat to type 08 and 10 When I turn the knob on the thermostat between 18.5/19/19.5, this is what I get from the log for the setpoint temperature: when 'info' the data from the thermostat is not recognized `Thermostat stats: not sure about the current room temperature, it currently says 18.5 degrees on the thermostat and this is what I get from log t |
|
sorry for the weird formatting. Not sure yet how i should properly copy/paste code in here |
|
for fomatting large chunks of code use 2 or 3 backquotes ` |
|
if you do an |
|
Also does your thermostat show the actual room temperature too? Was it 19.1 degrees by any chance? |
|
with and Yes my thermostat shows the actual room temperature, it rounds of to half a degree and at the time it was jumping between 18.5 and 19 so I think the 19.1 that you found was definitely the actual room temperature measured by the thermostat, seems like you are on the good track :) :) that's great! |
|
right, I forgot the sending/Tx doesn't work with Junkers yet, which is used to query the devices. There's another issue related to that problem which is waiting for a logic analyzer to see what is blocking the traffic. So it may be a while until someone has figured it out. |
|
which is this one: #103 |
|
can you try again with the latest dev built and set tx_mode to 2 ? |
|
closing. The values from an FR10 should be picked up, otherwise please re-open |
|
hey proddy, now that heating season started again and i'm home since a long while (just shortly unfortunately), I finally found time to flash 1.8.3 on the wemos and I confirm that the FR10 is indeed recognized now and room termperature and setpoint are being read correctly! That's awesome!! Hopefully you bright minds can figure out a way to change the setpoint. |
|
sure, I'll send over some commands you can test using telnet to get things going. BTW the current version is 1.9.1 which has some more improvements (and a web interface). There are some reports of issues with Junkers HT3 so I would stick with 1.9.0 or 1.8.3 for now. |
|
and anything in the |
|
nope, it says tx queue is empty. Also after I do an autodetect quick |
|
I scrolled back a bit in this topic and did a not sure if any of this is helpful or related |
|
yes, that is helpful. let me think about it and run some tests |
|
err hang on, if you're on Junkers I would actually expect send When you type |
|
It doesn't specifically say the protocal is Junkers. I'm on 1.9.1b10, tx_mode 3 info |
|
the protocol is in the latest build from yesterday. |
|
oh my bad, I'm always looking for the latest release here https://github.com/proddy/EMS-ESP/releases/tag/1.9.0 and find |
|
ok, got 1.9.1b11 now and it says this Doesn't look like send 8B 08 02 00 20 finds the boiler, The Thermostat is still recognized by sending the other telegram |
|
ok, good, its recognized as Junkers. what does also with logging, can you send over the output for |
|
Doesn't look like that is bringen back the boiler |
|
I hate to ask, but does |
|
my Junkers boiler was automatically detected in both versions so I don't think I ever sent this one but I'll reflash the wemos with both precompiled firmwares and let you know |
|
hang on with re-flashing, I had another brain wave.... |
|
I'm still confused. But have a new build - nothing has changed so don't expect it all to work, but I want to try one more thing. to see the send messages and responses. BTW would be better if we used Gitter to chat than GitHub postings? |
yeah probably not a bad idea...I'm new to this, but I signed in to Gitter with my github account, so I assume my username is the same? |
|
the gitter channel is https://gitter.im/EMS-ESP/community# |
|
arrgghh, this is all confusing and hurting my head! Can you try |
|
Yeah! |
|
ok, found the issue and fixed it. It wasn't in a piece of code I wrote so it took some time figuring it out. Apparently this has been a problem in 1.9.0 too. Can you test b12? |
|
@proddy it works, thanks a lot ! |
|
I can confirm that b12 works here as well! Thanks a lot Proddy! |
|
ah cool. thanks guys for testing. I'll push 1.9.1 to master. |
Hi Proddy,
awesome work, thanks a lot!
I have a question, my boiler is a junkers cerapur comfort TOP 30-3 but is automatically recognized as a Bosch condens 2500. Not a big problem in the end because i can read the values and they seem to be correct. That's great!
My thermostat is not automatically recognized however. It's a junkers FR10. Could you implement it in the list please, when you find the time. Which logs do you need for that?
I'm quite new with this github and i'm not a coder so apologies if i'm not following protocol.
This is an extract of what i get from verbose logging:
System Logging set to Verbose
(00:08:14.231) 0x10 -> all, type 0xFF telegram: 90 00 FF 00 00 6F 03 01 00 BE 00 BE (CRC=85), #data=8
(00:08:14.490) 0x10 -> Boiler, type 0x16 telegram: 90 88 16 00 18 (CRC=B5), #data=1
(00:08:14.522) Boiler -> 0x10, type 0x16 telegram: 88 10 16 00 FF 58 55 00 00 F7 0F 01 05 64 0A 01 (CRC=86), #data=12
(00:08:14.698) Boiler -> all, type 0x18 telegram: 88 00 18 00 41 02 80 55 3A 09 03 25 C0 01 B2 80 00 01 BE FF FF 0E 00 00 00 00 00 02 18 (CRC=AF), #data=25
(00:08:14.938) Boiler -> all, type 0x34 telegram: 88 00 34 00 2B 01 B2 80 00 A1 00 00 01 00 00 1E 7E 00 0E CC 00 (CRC=C9), #data=17
(00:08:15.618) 0x10 -> Boiler, type 0x02 telegram: 90 88 02 00 0A (CRC=F7), #data=1
(00:08:15.643) Boiler -> 0x10, type 0x02 telegram: 88 10 02 00 5F 12 0D 00 00 00 00 00 00 00 (CRC=29), #data=10
Boiler found. Model Bosch Condens 2500 with TypeID 0x08, ProductID 95, Version 18.13
Requesting type UBAMonitorFast(0x18) from dest 0x08
Requesting type UBAMonitorSlow(0x19) from dest 0x08
Requesting type UBAParameterWW(0x33) from dest 0x08
Requesting type UBAParametersMessage(0x16) from dest 0x08
Requesting type UBATotalUptimeMessage(0x14) from dest 0x08
(00:08:18.616) 0x10 -> Boiler, type 0x23 telegram: 90 08 23 00 42 (CRC=5F), #data=1
(00:08:18.649) 0x10 -> Boiler, type 0x23 telegram: 90 08 23 02 00 (CRC=19), #data=1
(00:08:18.682) 0x10 -> Boiler, type 0x1A telegram: 90 08 1A 00 42 (CRC=BB), #data=1
(00:08:18.706) 0x10 -> Boiler, type 0x1A telegram: 90 08 1A 02 00 (CRC=FD), #data=1
(00:08:24.652) Boiler -> all, type 0x18 telegram: 88 00 18 00 42 02 83 55 3C 09 03 25 C0 01 B3 80 00 01 C0 FF FF 0E 00 00 00 00 00 02 18 (CRC=2C), #data=25
(00:08:24.861) Boiler -> all, type 0x34 telegram: 88 00 34 00 2B 01 B3 80 00 A1 00 00 01 00 00 1E 7E 00 0E CC 00 (CRC=DF), #data=17
(00:08:26.452) 0x10 -> Boiler, type 0x23 telegram: 90 08 23 00 41 (CRC=5C), #data=1
(00:08:26.485) 0x10 -> Boiler, type 0x23 telegram: 90 08 23 02 00 (CRC=19), #data=1
(00:08:26.517) 0x10 -> Boiler, type 0x1A telegram: 90 08 1A 00 41 (CRC=B8), #data=1
(00:08:26.542) 0x10 -> Boiler, type 0x1A telegram: 90 08 1A 02 00 (CRC=FD), #data=1
Thanks a lot in advance for having a look.
The text was updated successfully, but these errors were encountered: