Unrecognized EMS device (device ID 0x17, product ID 65) - Thermostat Buderus, RC 10

[karoti4]

I bought a BBQkees gateway S32 a few days ago. I connected the gateway to the boiler (Buderus Logamax Plus GB022) and the following problems occurred. Please help.

1. Thermostat Buderus RC 10 is not recognized. I don't know if it's a software/ library problem or a hardware problem?
2. Tx - LOW (67%) boiler is connected via EMS screw terminal - I tried to set all Tx modes with no result. I tried to connect a thermostat, with different cables of different lengths with no result (Tx line quaility was 65 - 75%).
   
3. Tx Errors - mostly:
   

Is it possible that points 2 and 3 are related to point 1?

RC 10 - label screenshot:

log.txt
emsesp_system_info (5).txt
emsesp_system_settings (4).txt

[proddy]

Thanks for the clear write-up! I'm not sure points 2 and 3 are related but I've added your thermostat to the latest dev build (version 3.2.2b12) so give that a try and we'll take it from there.

[karoti4]

Thanks for the clear write-up! I'm not sure points 2 and 3 are related but I've added your thermostat to the latest dev build (version 3.2.2b12) so give that a try and we'll take it from there.

Thank you, for a quick response.

I uploaded a new firmware and now this message pops up:

log (1).txt
emsesp_system_info (8).txt
emsesp_system_settings (7).txt

[proddy]

maybe the old version is cache. to be sure do a ctrl-shift-R in the web page. Also set your tx mode to EMS (1)

[karoti4]

The cache is clearedm EMS set to 1 - with no change.

[bbqkees]

Check if the board profile is still on S32. If you have a Buderus system TX mode 1 is usually the right one.

[proddy]

Tx mode and board profile look fine. It looks like there is just no Tx since no devices are detected and there are no Tx errors I can see. Could be a faulty cable?

[bbqkees]

Indeed check the wiring. Also try to swap the wires on the screw terminal.

[MichaelDvP]

Seems to be a uncommon boiler/contoller, not responding to 10, 11, 1C, 14 telegrams. The 14 is fetched every minute, but normally also broadcasted, i think we can skip the fetch to reduce tx-errors.

I think the missing devices communication with dev is the waiting for master-poll of KM200 (0x48 device) and this boiler/controller does not send it. We should add a timeout for the send delay if there is no 0x48 in a minute.

@proddy Should i fix it and push, or do you have other changes in pipeline?

[proddy]

@MichaelDvP how did you know about the KM200 controller? I couldn't see if from the logs. Your fix makes sense if the KM200 is not returning a poll. I'm only working on the network code (#161)

[MichaelDvP]

how did you know about the KM200 controller? I couldn't see if from the logs. Your fix makes sense if the KM200 is not returning a poll.

@proddy This was the change from #90, we are only waiting for the poll from master to 0x48, not for the reply of km200. But it seems this boiler is older than km200/modem devices and does not send out this poll.

@karoti4 Please check with new dev (version unchanged) if my assumption was right.

[karoti4]

how did you know about the KM200 controller? I couldn't see if from the logs. Your fix makes sense if the KM200 is not returning a poll.

@proddy This was the change from #90, we are only waiting for the poll from master to 0x48, not for the reply of km200. But it seems this boiler is older than km200/modem devices and does not send out this poll.

@karoti4 Please check with new dev (version unchanged) if my assumption was right.

@MichaelDvP OK, thank you, I'll try it in the evening.

[karoti4]

I appreciate and thank you for your quick feedback and help.

Actual state after uploading last EMS-ESP Version v3.2.2b13 is:

1. Tx is OK 👍
   

2. Thermostat RC10 is recognized, but there are no data available for this device (for me mainly temperature):
   

3. I tried change few editable boiler parameters - some of them works, some not - maybe the parameters that do not work are related to the thermostat (but there is no data) or my boiler does not support them.

emsesp_system_info (10).txt
log (2).txt
emsesp_system_settings (9).txt

[proddy]

telnet (use telnet on wsl/linux or ptty on windows) to ems-esp.local and then type watch 17. Grab about 50-100 lines and post it here

[karoti4]

OK - here is the log:

watch_17_log.txt

[proddy]

looks like the thermostat isn't sending any temperature data back to the boiler. @MichaelDvP any ideas?

[MichaelDvP]

Looks like this thermostat is sending telegram 0xAE and is compatible with RC20_N, not with RC10. I've changed it in database, @karoti4 please check.

[karoti4]

Thank you all for, help. I´m happy now.

[proddy]

horray!

[proddy]

Seems to be a uncommon boiler/contoller, not responding to 10, 11, 1C, 14 telegrams. The 14 is fetched every minute, but normally also broadcasted, i think we can skip the fetch to reduce tx-errors.

@MichaelDvP the 0x14 isn't broadcasted on some boiler systems (not mine which is a Nefit CR20). It was also reported by a user "Project" in Discord this morning. So I'll add it back.

[projectile25]

Hi , that was me on Discord . When helps the system is Buderus Logamax plus GB132 with RC35.

[MichaelDvP]

No problem anymore, we can fetch this telegram and if karoti4s boiler does not reply, the telegram fetch is toggled (because of this). The log is not flooded with tx-errors and boilers with telegram 14 like GB132 are polled.