… kann ich gern machen… >> aber wie schreibe ich Dir per PM? (sorry)
Was hast Du für eine WP (WKF?/ HTS? / Firmware / Baujahr /evtl. Seriennummer?
Hi, great to find a Remko integration for homeassistant!
I’m new to MQTT and am probably making a trivial mistake.
I managed to connect our WKF100 running 4.27 with a bridged connection from Mosquitto, and am getting a few results. But it seems I allways get the resultset from the smartweb homepage (ie Information (User)) - even when I hardcode a querylist in the heatpump.py code… The smartweb homepage is identified by valuepair “5074” : “024d”. But smartweb is not running, and as far as I can find out the intgeration is not sending these values (I am new to python as well so I may be mistaken).
I’ve added a part of the log. Hope someone can help me out.
PS. Antworten auf Deutsch ist OK, ich verstehe das prima, aber kenn mich nicht aus mit schreiben…
2025-03-01 19:48:01.866 DEBUG (MainThread) [custom_components.remko_mqtt.heatpump] KEEP_ALIVE topic:[V04P27/SMTID/CLIENT2HOST]
2025-03-01 19:48:01.866 DEBUG (MainThread) [custom_components.remko_mqtt.heatpump] KEEP_ALIVE payload:[{"FORCE_RESPONSE": "true", "query_list": "[1079, 1082, 1893, 1894, 1951, 1972, 1974, 5001, 5006, 5027, 5032, 5039, 5049, 5050, 5051, 5055, 5064, 5069, 5075, 5085, 5131, 5145, 5232, 5320, 5321, 5626, 5693, 5803, 5998]"}]
2025-03-01 19:48:01.874 DEBUG (MainThread) [custom_components.remko_mqtt.heatpump] MESSAGE_RECEIVED remko: message.payload:[V04P27/SMTID/CLIENT2HOST] [{"FORCE_RESPONSE": "true", "query_list": "[1079, 1082, 1893, 1894, 1951, 1972, 1974, 5001, 5006, 5027, 5032, 5039, 5049, 5050, 5051, 5055, 5064, 5069, 5075, 5085, 5131, 5145, 5232, 5320, 5321, 5626, 5693, 5803, 5998]"}]
2025-03-01 19:48:01.874 DEBUG (MainThread) [custom_components.remko_mqtt.heatpump] MESSAGE_RECEIVED remko: message.payload:[V04P27/SMTID/CLIENT2HOST] [{"FORCE_RESPONSE": "true", "query_list": "[1079, 1082, 1893, 1894, 1951, 1972, 1974, 5001, 5006, 5027, 5032, 5039, 5049, 5050, 5051, 5055, 5064, 5069, 5075, 5085, 5131, 5145, 5232, 5320, 5321, 5626, 5693, 5803, 5998]"}]
2025-03-01 19:48:02.061 DEBUG (MainThread) [custom_components.remko_mqtt.heatpump] MESSAGE_RECEIVED remko: message.payload:[V04P27/SMTID/HOST2CLIENT] [{"values": {"5999": "01", "3130": "21", "1152": "01", "5255": "03"}, "CLIENT_ID": "8034283A5EE2", "SMT_DEV": 236}]
2025-03-01 19:48:02.061 DEBUG (MainThread) [custom_components.remko_mqtt.heatpump] MESSAGE_RECEIVED remko: message.payload:[V04P27/SMTID/HOST2CLIENT] [{"values": {"5999": "01", "3130": "21", "1152": "01", "5255": "03"}, "CLIENT_ID": "8034283A5EE2", "SMT_DEV": 236}]
2025-03-01 19:48:02.626 DEBUG (MainThread) [custom_components.remko_mqtt.heatpump] MESSAGE_RECEIVED remko: message.payload:[V04P27/SMTID/HOST2CLIENT] [{"values": {"3950": "02", "5029": "0009", "1014": "06", "1726": "00", "1727": "00", "1937": "01", "1938": "00", "1976": "0000", "1978": "00", "1979": "00", "5198": "21", "5074": "024D", "5106": "0000", "5109": "0000", "1935": "02030700", "5292": "0000000000000000000000000000000000000000", "5182": "9287B52CFF7F9CE4", "5998": "09", "1082": "01F4", "1088": "02", "1137": "01", "1220": "01C2", "1249": "00", "1946": "0000", "1951": "01", "1967": "00", "5001": "09", "5034": "00DC", "5039": "020D", "5055": "0028", "5102": "01", "5148": "02", "5229": "1E2E13", "5230": "0001000307E9", "5240": "8A", "5578": "0000", "5763": "01", "5870": "0000"}, "SMT_STATUS_FLAGS": 1, "LASTWRITE": 1740854799, "CLIENT_ID": "DCE5332015D2", "SMT_DEV": 33}]
2
Still don’t know what went wrong, but replaced @Altrec’s integration with the remko_mqtt-ha integration from @hante which worked out-of-the-box. Even managed to add extra sensors 
Hi Jan,
ich hatte mit der aktuellen Version von Altrec auch Probleme mit der Firmware 4.26 Vermutlich ist sie für 4.28 besser geeignet. Ich habe die gleiche Lösung wie du im Einsatz.
Hi all, I’m trying to decrease the room-temperature at night by changing the colder/hotter value. This means a “default” temperature of 20.0C is decreased or increased by the colder/hotter value.
My findings are colder/hotter only has effect when you setup the “gemischter kreis” to be controlled from “control-panel” instead of the Easy-Control thermostat (which is mounted in the livingroom)…. But when I do that the target-room-temperature (ie. the Easy Control thermostat) is no longer updated / pushed over mqtt by the heatpump.
Does anyone know how to monitor that “default” temperature? I’ve tried every target-room-temperature sensor I could find (5075, 5077, 5767, 5776 and 5848…)
For the record: I’m running 4.27 on a WKF100. Maybe this is not an issue on 4.28?
Hallo Jan,
ich hatte Codebeispiele von @Torbeen bekommen in den er den folgenden Code für die Raumtemperaturen benutzt.
- state_topic: "V04P26/SMTID/HOST2CLIENT"
name: Raumtemperatur Ist Wärmepumpe
value_template: '{{ value_json["values"]["5050"] | int(base=16) / 10 }}'
unit_of_measurement: °C
- state_topic: "V04P26/SMTID/HOST2CLIENT"
name: Raumtemperatur Soll Wärmepumpe
value_template: '{{ value_json["values"]["5075"] | int(base=16) / 10 }}'
unit_of_measurement: °C
Für die Änderung der Raumtemperatur benutzt @Torbeen die folgende Automatisierung.
alias: Raumtemperaturgeber (Wohnraum) für Wärmepumpe
sequence:
- data:
topic: V04P26/SMTID/CLIENT2HOST
payload: >2-
{
"FORCE_RESPONSE": true,
"values": {
"5050": "{{ states('sensor.temp_wohnraum_eg_hex_4') }}"
}, "query_list": [1082, 1088, 1137, 1220, 1249, 1946, 1951, 1967,
5001, 5034, 5039, 5055, 5148, 5229, 5230, 5240, 5255, 5578, 5763,
5870], "CLIENT_ID": "SMT033I0000000000000000", "LASTWRITE":
1670664457, "SMT_USER": 0, "ISTOUCH": false, "DEVID":
"DCE53321B1FA" }
action: mqtt.publish
mode: single
icon: mdi:refresh-auto
description: ""
Statt dem Wert eines Sensors kannst du auch die Temperatur direkt schreiben. Hier ein Beispiel mit 20°C.
alias: Raumtemperaturgeber (Wohnraum) für Wärmepumpe
sequence:
- data:
topic: V04P26/SMTID/CLIENT2HOST
payload: >2-
{
"FORCE_RESPONSE": true,
"values": {
"5050": "0{{ '%0x' % (20 | int(0) * 10) }}"
}, "query_list": [1082, 1088, 1137, 1220, 1249, 1946, 1951, 1967,
5001, 5034, 5039, 5055, 5148, 5229, 5230, 5240, 5255, 5578, 5763,
5870], "CLIENT_ID": "SMT033I0000000000000000", "LASTWRITE":
1670664457, "SMT_USER": 0, "ISTOUCH": false, "DEVID":
"DCE53321B1FA" }
action: mqtt.publish
mode: single
icon: mdi:refresh-auto
description: ""
Die “query_list” würde ich an deiner Stelle nach den abgefragten Registerwerten, die du verwendest, prüfen. . Am besten du nimmst die gleiche “query_list”, die du auch für die regelmäßige MQTT Anforderung verwendest, andernfalls schläft die MQTT Antwort nach einer gewissen Zeit ein. Vielleicht ist die regelmäßige MQTT Anforderung über die “query_list” auch dein Problem. Hast du eine Automatisierung, die die “query_list” sendet, eingestellt?
VG
Hi Jan,
If I’m not mistaken than you have a room thermostat (by Remko) and you you want to overrule/bypass it at night. To be clear; I dont have such a thermostat and my WP is controlled in total different way. So that is why I’m asking. Anway, assuming that that is what you want then I can imagine that the Remko WP does not like what you tried. Either the thermostat is setting target temp or the control panel and the control panel uses this 20.0C +/- configured offset.
There are two options that come to mind. Either find an correction setting for your thermostat. Don’t know if it exists, but like 2015, it allows you to correct the outside temp, I use that because the outside temp measured is off by 1.0C in my case. Since I don’t have a thermostat I cant see if there is such a correction available.
Secondly I wonder is if it not possible to simply update the thermostat setting? I would expect that the thermostat results in an MQTT update. You could try to monitor MQTT by using Addon MQTT Explorer and adjust the temp on your control panel and see if you can determine which setting gets updated (maybe 5004?) Quite tricky though as typically you’ll see many updates, you may want to stop the Remko integration and kill all browser tabs towards your Remko (if using local IP) when running MQTT explorer. Note: you can use this explorer also to test commands. So you create your own experimental string and update a field to test things.
good luck
Hi Hante,
I tried to setup a configuration similar to yours, that is: using the control panel (20C default temp) and offsetting it with the desired change. But it seems the necessary sensor (Remko Raumtemperatur sensor) is not installed… So I’ll have that installed and see if it will work.
What is weird is that the actual room temp is no longer updated by Remko when the setting is changed to “control panel”. In my case it got stuck at 24.8C both on Homeassistant and on the touchscreen on the heatpump.
I’d rather not tamper with the room thermostat or outside temp just to set the soll-temp. If for some reason someone wants to change the temp, or when Homeassistant is not working correctly it will be hard to explain my family how to proceed.
But I will take a look at the MQTT addon, up till now I’ve used the standalone MQTT explorer.
BTW. Doesnt Remko provide a setting to offset the outside temperature? They do for their thermostat…
Hi Oliver,
If I read your code correctly you are updating the ist-temperature. My guess is that in that way my automation would compete with the Remko- thermostat. And since Remko-thermostat also sends the soll-temperature to the heatpump there would be competition for that value as well.
What I mean is this: my automation and the Remko-thermostat send different values to the heatpump it will force the heatpump to frequent changes. Especially for the soll-temperature that will cause problems (at least extra compressor starts and thus extra wear).
Having said that I might disconnect the Remko thermostat and have Homeassistant update the ist- and soll-temperature - kind of simulating the Remko thermostat . Not quite sure how the heatpump will react since the thermostat is set up in the Remko “heizkreis” settings.
And, to answer you question: I do have an automation running that sets the offset temperature (colder/hotter). It runs 5 times a day (without effect since setting the colder/warmer offset currently doesnt work properly since the heatpump misses the required “Raumtemperatur” sensor. So far I rarely loose connection, maybe because a dashboard is permanently running since I’m still testing. I might trigger the automation more frequently (I hope once an hour will be enough).
Hi Oliver,
I’ve tried to update both the ist- and soll-temp by registering them as type temperature_input but it seems my WKF100 doesnt accept changes.
In the processI managed to loose connection. Even after reloading/reinstalling MQTT/Mosquitto and the remko_mqtt-ha integration and many many HA restarts I couldnt reconnect and finally gave up and started from scratch (fresh HA with MQTT/Mosquitto and remko_mqtt-ha…). This is now running for 2 days and seems stable.
I also had a visit from a Remko engineer who finetuned my heatpump settings and will be back to upgrade to a recent version and install the Remko humidity and temperature sensor.
We had a discussion on how to alter the temperature, and his idea is offsetting the temperature (hotter/colder) should work, even with my roomthermostat. So what I’ve done is added 5077 (target_room_temp + offset) to my querylist. I’ll first update the offset through the control panel - would rather not be bitten by connection problems again because I need the sensor data to see if it works.
UPDATE: offsetting the temperature has no effect when the roomthermostat (EasyConnect EC-1) is controlling the heatpump. This will (probably) work when the heatpump is controlled by the control-panel - for that the Remko temperature- and humidity-sensor must be installed.