FR100 set setpoint doesnt work

[dllaurent]

Hello, I received my s32 gateway a few days ago and I cannot define the temperature setpoint for the thermostat

Bug description

when I try to modify the setpoint temperature of any mode of the thermostat (heat, eco, nofrost), nothing changes on the thermostat but when I change the setpoint on the thermostat I see it clearly in my gateway

Device information
{
"System": {
"version": "3.2.2b14",
"uptime": "000+00:08:17.923",
"uptime_sec": 497,
"freemem": 164,
"reset_reason": "Software reset CPU / Software reset CPU"
},
"Status": {
"bus": "connected",
"bus protocol": "HT3",
"telegrams received": 345,
"read requests sent": 55,
"write requests sent": 5,
"incomplete telegrams": 0,
"tx fails": 0,
"rx line quality": 100,
"tx line quality": 100,
"MQTT publishes": 238,
"MQTT publish fails": 0,
"dallas sensors": 0,
"dallas reads": 0,
"dallas fails": 0
},
"Devices": [
{
"type": "Boiler",
"name": "Condens 2500/Logamax/Logomatic/Cerapur Top/Greenstar/Generic HT3 (DeviceID:0x08, ProductID:95, Version:23.00)",
"handlers": "0x10 0x11 0xC2 0x14 0x15 0x1C 0x18 0x19 0x1A 0x35 0x16 0x33 0x34 0x26 0x2A"
},
{
"type": "Thermostat",
"name": "Junkers FR10 (DeviceID:0x10 ProductID:111, Version:16.04)",
"handlers": "0xA3 0x06 0xA2 0x12 0x16F 0x170 0x171 0x172 0x165 0x166 0x167 0x168"
},
{
"type": "Controller",
"name": "HT3 (DeviceID:0x09, ProductID:95, Version:23.00)"
}
]
}

[MichaelDvP]

Please check with terminal the response of read 10 165 and read 10 179.

[dllaurent]

Please check with terminal the response of read 10 165 and read 10 179.

ems-esp:# read 10 165
000+01:03:10.312 D 92: [telegram] Tx read request to device 0x10 for type ID 0x165
000+01:03:10.454 D 93: [telegram] Sending read Tx [#220], telegram: 8B 90 FF 00 20 00 65
000+01:03:10.475 T 94: [emsesp] Me(0x0B) <- Thermostat(0x10), JunkersSet(0x165), data: 20
000+01:03:10.499 D 95: [emsesp] Last Tx read successful
000+01:03:10.499 N 96: [emsesp] Thermostat(0x10) -> Me(0x0B), JunkersSet(0x165), data:
000+01:03:10.499 D 97: [emsesp] This telegram (JunkersSet) is not recognized by the EMS bus
000+01:03:10.499 D 98: [emsesp] Toggling fetch for device ID 0x10, telegram ID 0x165 to 0
000+01:03:10.499 D 99: [emsesp] No telegram type handler found for ID 0x165 (src 0x10)
000+01:03:10.508 D 100: [mqtt] Publishing topic ems-esp/response (#1292, retain=0, retry=1, size=77, pid=1)

ems-esp:# read 10 179
000+01:03:14.257 D 103: [telegram] Tx read request to device 0x10 for type ID 0x179
000+01:03:14.359 T 104: [emsesp] Boiler(0x08) -> All(0x00), UBAMonitorWW(0x34), data: 32 01 07 80 00 81 00 00 01 00 00 53 01 00 44 C5 00
000+01:03:14.584 D 105: [telegram] Sending read Tx [#221], telegram: 8B 90 FF 00 20 00 79
000+01:03:14.605 T 106: [emsesp] Me(0x0B) <- Thermostat(0x10), ?(0x179), data: 20
000+01:03:14.653 D 107: [emsesp] Last Tx read successful
000+01:03:14.653 N 108: [emsesp] Thermostat(0x10) -> Me(0x0B), ?(0x179), data: 01 08 10 4B 03 14 25 28
000+01:03:14.653 D 109: [emsesp] No telegram type handler found for ID 0x179 (src 0x10)
000+01:03:14.676 D 110: [mqtt] Publishing topic ems-esp/response (#1293, retain=0, retry=1, size=83, pid=1)

[dllaurent]

Thanks, if i understand correctly i have to recompile and retest ?

[MichaelDvP]

You can also use the precompiled dev-bin from here.

[dllaurent]

Thanks you, i will test this later, have a nice day

[dllaurent]

thank you very much, it works perfectly.

[proddy]

great, closing. Thanks Michael.