LAN-Anbindung für BSB-Bus (Brötje, Elco Thision etc.)

[Schotty]

The result in attachment

Thanks!
I noticed two things:
1. It already says 131 wireless room unit 1 missing and 131 wireless room unit 2 present, so I guess you already switched the QAA to circuit2, right?
2. 750 room-influence for circuit1 says 30%, but 1050 room-influence for circuit2 says ---% - so judged by that, you didn't activate room-influence for the second circuit?! Afaik you need to activate that, otherwise a given room temperature for the second circuit has no effect / won't be taken into account. Try to also set it to 30% for example.

Btw: The error-logs (6800-6891) show the missing temp sensor every ~11 minutes, which was exactly the same behaviour wit the outside temp sensor, when it was disconnected and no value was transmitted. After transmitting a value, the error symbol disappeared again.

[AntFleu]

1. It already says 131 wireless room unit 1 missing and 131 wireless room unit 2 present, so I guess you already switched the QAA to circuit2, right?

It's right
For the moment, i have no errror, but if i remember well. The error start at midnight.
Maybe a link with that:

Fühler
Zeilennr. Bedienzeile
6200 Fühler speichern
Um Mitternacht speichert das Grundgerät die Zustände an den Fühlerklemmen ab,
sofern der Regler zuvor während mindestens zwei Stunden in Betrieb war.
Fällt nach der Speicherung ein Fühler ab, generiert das Grundgerät eine
Fehlermeldung.
Durch diese Einstellung können die Fühler sofort gespeichert werden. Dies wird nötig
wenn z.B. ein Fühler entfernt und nicht mehr benötigt wird.
Zeilennr. Bedienzeile
6201 Fühler löschen
Mit dieser Einstellung werden alle angeschlossenen Fühler gelöscht. Die Fühler
werden neu eingelesen mit der Funktion ,,Fühler speicher" (6200) oder automatisch um
Mitternacht, sofern der Regler zuvor während mindestens zwei Stunden in Betrieb war.

I

2. 750 room-influence for circuit1 says 30%, but 1050 room-influence for circuit2 says ---% - so judged by that, you didn't activate room-influence for the second circuit?! Afaik you need to activate that, otherwise a given room temperature for the second circuit has no effect / won't be taken into account. Try to also set it to 30% for example.

Oops, I forgot to set again this param. I was all reset after my last try the first november

Now, i will start a capture from arduino IDE.

Thanks

[Schotty]

Hi,
this is nothing exciting, nothing new and I guess also nothing that helps us with the problem of @AntFleur, but I wanted to share it:
I did some tests with an RVS63-unit and a QAA55 as a room unit (the QAA55 basically works like the QAA75, it's just limited in functionality).
The RVS is a testsystem with (right now) resistors for fix temperatures like outside-temp, boiler-temp and water-temp. Therefore there is no change in the burnerstate, I have to check the state of the relais for the pumps of the circuits (by the sound of the acting relais and by 8730&8760).

I did NOT change anything in 6200 or 6201 and I never got any error-message about a (missing) room unit / room temp, even when no temp was available.
Result: Temp transmissions (for both circuits) were successful and the controller reacted to different values as expected (e.g. turning on the pump when a room temp was too low). When no temp was available, it seemed that the controller just worked 'regularly'.

I did the following for both circuits (1 and 2):

1. I activated circuit 1&2 in the heater config (5710&5715) and set the room influence (750&1050) to 20%.

2. Without the QAA connected, I transmitted & checked different room temps via BSB-LAN, changed the state of the circuits (automatic/comfort/reduced) and watched the behaviour of the pump-relais. After every change I made I checked the specific parameters to see if the transmission was successful and if/how the behaviour of the controller was affected. Everything worked fine.

3. I measured the time when the controller lost the room temp. This is kinda weird: it seemed that circuit 1 held the temp longer (nearly double of time) then circuit 2. C1 lost the temp in a range between 11-16minutes, C2 lost it in a range between 4-8minutes (further testing for validation would be necessary).
But: Both circuits never triggered an error message when the temp was lost/not available.

4. I connected the QAA55 room unit and defined it as room unit for circuit 1. No problems. The room unit got powered up and started transmitting the temp every minute by itself. In this time I send temp for c2 and also waited until the value was lost - no problems/error messages occured.
After a while I changed the setting an defined QAA as room unit for circuit 2 - same tests, same behaviour, no problems.

@AntFleur: You're using a QAA78 (which is the wireless version of the QAA75) - right? So I can/will repeat the tests with a QAA75 room unit. Also I can/will check if the room temp is transmitted to both circuits when it's configured as a controller for both circuits. Could this maybe be an option for you or do you have / are you transmitting different temp values for c1 & c2?

I know, thats all nothing new but right now I keep asking myself
a) why c2 doesnt seem to hold the temp as long as c1,
b) what, why and when (only when the temp is lost?) at AntFleurs RVS21 triggers an error message,
c) if its necessary for @AntFleur to run 6200 after connecting a room unit. For c): At least in the manuals of the room units 6200 isn't mentioned, so also from the 'official' side it  doesn't seems to be necessary.

[AntFleu]

Hi,
I made very little progress but here are my first tests.
1 - Use the serial monitor to see anything with the room sensor on C2.
--> Nothing, even when i changed the room setpoint or warmed up the sensor. The only thing, when i changed the status of the heat pump (eg. confort to reduced)
2 - Waiting one night, always with room sens on C2 and BSB-LAN for C1
--> The next morning no error message for the sensor,(what!  )
3 - This same morning, i inverted the sensor, errase the sensors 6201, forced 6200 and go to job
--> At midday (10 min from my job ) no error message.
4 - Changed the time on the heat pump at 23:15 about and go to job
.

Um Mitternacht speichert das Grundgerät die Zustände an den Fühlerklemmen ab,
sofern der Regler zuvor während mindestens zwei Stunden in Betrieb war.
Fällt nach der Speicherung ein Fühler ab, generiert das Grundgerät eine
Fehlermeldung.
Durch diese Einstellung können die Fühler sofort gespeichert werden. Dies wird nötig
wenn z.B. ein Fühler entfernt und nicht mehr benötigt wird.

--> Error messages are back, when i looked my logs the firts started at 00:03

Code Auswählen Erweitern

51060462 04.11.2019 23:59:02 8326 LAN->HEIZ QUR DC C2 00 0B 06 3D 11 30 5F 43 E6
51060530 04.11.2019 23:59:02 8326 HEIZ->LAN ERR DC 80 42 0C 08 11 3D 30 5F 07 6C 8C
51073300 04.11.2019 23:59:15 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 2C 00 8A E6 20,7
51113208 04.11.2019 23:59:55 UNKNOWN DISP->ALL  INF DC 8A 7F 14 02 05 00 00 9D 00 FF 0A 19 FF FF FF FF 16 28 EA
51113336 04.11.2019 23:59:55 10102 HEIZ->ALL  INF DC 80 7F 15 02 2D 00 02 11 03 02 24 84 FF FF FF FF 00 01 3D DF
51113468 04.11.2019 23:59:55 10103 HEIZ->ALL  INF DC 80 7F 15 02 2E 00 02 11 03 02 24 84 FF FF FF FF 00 01 B0 7C
51113611 04.11.2019 23:59:55 UNKNOWN DISP->ALL  INF DC 8A 7F 14 02 05 00 00 9E 00 FF 03 19 FF FF FF FF 16 B2 E9
51114971 04.11.2019 23:59:57 1602 HEIZ->ALL  INF DC 80 7F 0E 02 31 00 02 12 01 00 4D 57 7F 256
51120447 05.11.2019 00:00:02 8326 LAN->HEIZ QUR DC C2 00 0B 06 3D 11 30 5F 43 E6
51120513 05.11.2019 00:00:02 8326 HEIZ->LAN ERR DC 80 42 0C 08 11 3D 30 5F 07 6C 8C
51131388 05.11.2019 00:00:13 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 30 00 CC F8 20,8
51180432 05.11.2019 00:01:02 8326 LAN->HEIZ QUR DC C2 00 0B 06 3D 11 30 5F 43 E6
51180496 05.11.2019 00:01:02 8326 HEIZ->LAN ERR DC 80 42 0C 08 11 3D 30 5F 07 6C 8C
51190071 05.11.2019 00:01:12 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 30 00 CC F8 20,8
51207351 05.11.2019 00:01:29 0 DISP->ALL  INF DC 8A 7F 14 02 05 00 00 6C 00 77 0B 05 02 00 01 25 00 13 80
51240419 05.11.2019 00:02:10 8326 LAN->HEIZ QUR DC C2 00 0B 06 3D 11 30 5F 43 E6
51240489 05.11.2019 00:02:10 8326 HEIZ->LAN ERR DC 80 42 0C 08 11 3D 30 5F 07 6C 8C
51248527 05.11.2019 00:02:18 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 30 00 CC F8 20,8
51266364 05.11.2019 00:02:36 10104 HEIZ->ALL  INF DC 80 7F 15 02 2F 00 02 11 00 00 FF FF FF FF FF FF 00 00 83 90
51285651 05.11.2019 00:02:55 UNKNOWN HEIZ->ALL  INF DC 80 7F 1C 02 05 00 02 48 C7 00 27 10 D1 00 98 01 02 00 00 00 00 00 00 00 00 B1 5B
51285809 05.11.2019 00:02:55 10100 HEIZ->ALL  INF DC 80 7F 0F 02 05 00 02 13 00 00 66 0B C4 74 102
51300487 05.11.2019 00:03:10 8326 LAN->HEIZ QUR DC C2 00 0B 06 3D 11 30 5F 43 E6
51300564 05.11.2019 00:03:10 8326 HEIZ->LAN ERR DC 80 42 0C 08 11 3D 30 5F 07 6C 8C
51305979 05.11.2019 00:03:15 UNKNOWN HEIZ->ALL  INF DC 80 7F 0D 02 05 00 00 69 38 41 18 95 56
51306103 05.11.2019 00:03:15 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 30 00 CC F8 20,8
51335779 05.11.2019 00:03:45 UNKNOWN HEIZ->ALL  INF DC 80 7F 0D 02 05 00 00 6B 41 06 FC 17 65


5 - I tried at two time to reproduce. 6201 (to delete the sens error) --> 6200 (to save sensor) and changed the time 5 min before midnight and 15 min the second time.
--> No error
6 - Since yesterday 21:00, i inverted again the temp sensor.
--> Today nothing errors and i want to wait this night again to be sure in a normal condition.

@AntFleur: You're using a QAA78 (which is the wireless version of the QAA75) - right? So I can/will repeat the tests with a QAA75 room unit. Also I can/will check if the room temp is transmitted to both circuits when it's configured as a controller for both circuits. Could this maybe be an option for you or do you have / are you transmitting different temp values for c1 & c2?

I using the QAA58 (the basic model) with AVS71.390/109 for the radio module. Thanks, but this is not a solution for me, my circuit 2 is for bed rooms and i want a lower temperature.

c) if its necessary for @AntFleur to run 6200 after connecting a room unit. For c): At least in the manuals of the room units 6200 isn't mentioned, so also from the 'official' side it  doesn't seems to be necessary.

Sorry, if I was not clear, 6200 only for test, i'm not sure if it has an impact. Cannot access to this setting without the OEM code from the heat pump.

Tomorrow, i will try again to generate the issue and look on the serial monitor.

Many thanks Schotty

[Schotty]

Hi,
I just sent you an email (sorry, couldnt get to it earlier)

Do you mean this error:

Code Auswählen Erweitern


51300564 05.11.2019 00:03:10 8326 HEIZ->LAN ERR DC 80 42 0C 08 11 3D 30 5F 07 6C 8C

??
Because
a) it also appeared just at the beginning of your log at 23:59 and
b) the parameter 8236 (referring to my list?!) is 'modulation of the burner' and not anything about a room temperature.
Besides that: in the complete query of /0-10000 you attached the other day, it doesnt even appear:

Code Auswählen Erweitern


8323 Diagnose Erzeuger - Gebläsedrehzahl: 1560 U/min
8400 Diagnose Erzeuger - Verdichter 1 K1: 0 - Aus

because -in my opinion- your heat pump doesnt have a 'modulating burner' like the gas-fired systems..

Or do you mean this entry:

Code Auswählen Erweitern


51285651 05.11.2019 00:02:55 UNKNOWN HEIZ->ALL  INF DC 80 7F 1C 02 05 00 02 48 C7 00 27 10 D1 00 98 01 02 00 00 00 00 00 00 00 00 B1 5B


Or this one:

Code Auswählen Erweitern


51305979 05.11.2019 00:03:15 UNKNOWN HEIZ->ALL  INF DC 80 7F 0D 02 05 00 00 69 38 41 18 95 56

??
This one also appears 30seconds later, but with an "65" at the end - maybe thats the temperature of something? EDIT: ah, you already wrote that in an earlier posting, just discovered it. Also there the '56' comes before the '65'. So if the 65 is the same error number as its displayed - is the '56' also an error number? I can't find a description about that anywhere..

Btw: I wonder what this one is about:

Code Auswählen Erweitern


51207351 05.11.2019 00:01:29 0 DISP->ALL  INF DC 8A 7F 14 02 05 00 00 6C 00 77 0B 05 02 00 01 25 00 13 80


What does the the error category 6800-6819 say right now?

Looking at your query you attached the other day:

Code Auswählen Erweitern


6800 Fehler - Historie 1 Datum/Zeit: 01.11.2019 18:30:00
6801 Fehler - Historie 1 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6802 Fehler - Historie 2 Datum/Zeit: 01.11.2019 18:19:00
6803 Fehler - Historie 2 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6804 Fehler - Historie 3 Datum/Zeit: 01.11.2019 18:08:00
6805 Fehler - Historie 3 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6806 Fehler - Historie 4 Datum/Zeit: 01.11.2019 17:57:00
6807 Fehler - Historie 4 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6808 Fehler - Historie 5 Datum/Zeit: 01.11.2019 17:46:00
6809 Fehler - Historie 5 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6810 Fehler - Historie 6 Datum/Zeit: 01.11.2019 17:35:00
6811 Fehler - Historie 6 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6812 Fehler - Historie 7 Datum/Zeit: 01.11.2019 17:24:00
6813 Fehler - Historie 7 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6814 Fehler - Historie 8 Datum/Zeit: 01.11.2019 17:13:00
6815 Fehler - Historie 8 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6816 Fehler - Historie 9 Datum/Zeit: 01.11.2019 16:11:00
6817 Fehler - Historie 9 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6818 Fehler - Historie 10 Datum/Zeit: 01.11.2019 15:46:00
6819 Fehler - Historie 10 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler

In the beginning the errors didnt appear every 10min, could it have been / be a transmission problem somehow? Did you check if the controller really got the transmitted temp?

[AntFleu]

I was talking about error 65

Code Auswählen Erweitern

51335779 05.11.2019 00:03:45 UNKNOWN HEIZ->ALL  INF DC 80 7F 0D 02 05 00 00 6B 41 06 FC 17 65
No issue this morning and grrr i forget to set again the logs after reset the arduino with room sensor on C2 and BSB LAN on C1.

What does the the error category 6800-6819 say right now?

which corresponds to the previously logs sent

Code Auswählen Erweitern

6800 Défaut - Historie 1 Datum/Zeit: 05.11.2019 05:00:00
6801 Défaut - Historie 1 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6802 Défaut - Historie 2 Datum/Zeit: 05.11.2019 04:49:00
6803 Défaut - Historie 2 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6804 Défaut - Historie 3 Datum/Zeit: 05.11.2019 04:38:00
6805 Défaut - Historie 3 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6806 Défaut - Historie 4 Datum/Zeit: 05.11.2019 04:27:00
6807 Défaut - Historie 4 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6808 Défaut - Historie 5 Datum/Zeit: 05.11.2019 04:16:00
6809 Défaut - Historie 5 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6810 Défaut - Historie 6 Datum/Zeit: 05.11.2019 04:05:00
6811 Défaut - Historie 6 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6812 Défaut - Historie 7 Datum/Zeit: 05.11.2019 03:43:00
6813 Défaut - Historie 7 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6814 Défaut - Historie 8 Datum/Zeit: 05.11.2019 03:32:00
6815 Défaut - Historie 8 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6816 Défaut - Historie 9 Datum/Zeit: 05.11.2019 03:21:00
6817 Défaut - Historie 9 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler
6818 Défaut - Historie 10 Datum/Zeit: 05.11.2019 03:10:00
6819 Défaut - Historie 10 Fehlercode: 65 - Raumtemperatur 2 Fühlerfehler

In the beginning the errors didnt appear every 10min, could it have been / be a transmission problem somehow? Did you check if the controller really got the transmitted temp?

No, transmission OK, the full logs in attachment (I had filtered to limit but as i have request for many parameters i have the logs for 8740 and 8770)

I have a friend who has to lend me a room sensor QA55. I will try to compare

Antoine

[Schotty]

The more I think about it, the more I (still) think that it must be some kind of a communication / transmission problem. Otherwise I'm running out of ideas..
Because: We can see, that in general the function with /I10001=xx works, 8770 gives us proof that the controller got the value:

Code Auswählen Erweitern


51248527 05.11.2019 00:02:18 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 30 00 CC F8     20,8
...
51250670 05.11.2019 00:02:20 8770 LAN->HEIZ QUR DC C2 00 0B 06 3D 2E 05 1E 08 F7
51250736 05.11.2019 00:02:20 8770 HEIZ->LAN ANS DC 80 42 0E 07 2E 3D 05 1E 00 05 30 A9 25     20,8

If it wouldnt work in general (e.g. a different command id) the controller wouldnt get the temp. So thats good.

But: One minute later it's getting weird:

Code Auswählen Erweitern


51306103 05.11.2019 00:03:15 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 30 00 CC F8     20,8
...
51308474 05.11.2019 00:03:18 8770 LAN->HEIZ QUR DC C2 00 0B 06 3D 2E 05 1E 08 F7
51308540 05.11.2019 00:03:18 8770 HEIZ->LAN ANS DC 80 42 0E 07 2E 3D 05 1E 40 0C 80 A9 CB     50

8770 says 50°C?!? What the heck?!?

Corresponding to that, the controller prompts the error message:

Code Auswählen Erweitern


51335779 05.11.2019 00:03:45 UNKNOWN HEIZ->ALL  INF DC 80 7F 0D 02 05 00 00 6B 41 06 FC 17 65


One minute later, the controller got the right temp again:

Code Auswählen Erweitern


51365792 05.11.2019 00:04:15 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 2C 00 8A E6     20,7
...
51368094 05.11.2019 00:04:17 8770 LAN->HEIZ QUR DC C2 00 0B 06 3D 2E 05 1E 08 F7
51368160 05.11.2019 00:04:17 8770 HEIZ->LAN ANS DC 80 42 0E 07 2E 3D 05 1E 00 05 2C 7A 98     20,7

No error message anymore.

Looking at your error logs 6800-6819 and starting with the last one (which was the 'earliest' at 03:10), the same like above happened again:

Code Auswählen Erweitern


62242366 05.11.2019 03:10:10 10001 LAN->HEIZ INF DC C2 00 0E 02 3D 2E 02 15 05 37 00 55 6F     20,9
...
62244606 05.11.2019 03:10:12 8770 LAN->HEIZ QUR DC C2 00 0B 06 3D 2E 05 1E 08 F7
62244672 05.11.2019 03:10:12 8770 HEIZ->LAN ANS DC 80 42 0E 07 2E 3D 05 1E 40 0C 80 A9 CB     50

with corresponding error 65 after that:

Code Auswählen Erweitern


62274012 05.11.2019 03:10:42 UNKNOWN HEIZ->ALL  INF DC 80 7F 0D 02 05 00 00 6B 41 06 FC 17 65


The same happened 11minutes later, until that everything was correct again.
I didn't check the whole log now for the rest of the error messages, but the above gave me this idea: just for testing if it triggers the error message, send /I10001=50 , check 8770 and watch out for the 65 error message. Maybe that would make sense (somehow) - a room temp of 50° would only occur if your sensor has a fault or if your house is burnig down..
But: I just tried with my testsystem, /I10001=50 worked, 8770 says 50°, no error message occured.. But maybe here its different to your controller..

@freetz: It's weird that this error with /I10001=xx and 8770=50 sometimes occurs every eleven minutes. Also its weird, that in that case 8770 always says 50° - no matter if the transmitted temp was 20.7 or 20.9 or so. Do you have any idea about that..?

[Luposoft]

Ein liebes Hallo an das Forum,

und zuallererst einen fetten Dank an die Entwickler und alle die hier so gut helfen.
Seit ich das BSB-LAN in Betrieb habe, hatte ich nicht einen Aussetzer. Läuft echt stabil. 

Ich habe mich weiter vorgearbeitet und kümmere mich nun um die Gerätefunktion 'Gasenergie' ID 8378-8383
Es handelt sich um eine ELCO Thision S Plus 19.

Leider wird der Wert nicht richtig angezeigt.

Am Beispiel von 8380:
Anzeige am Display der Heizung: 95728 kWh
Anzeige BSB-Lan: 30192 kWh


75 F0 -> 30192
01 75 F0 -> 95728

es scheint nur mit den 1. beiden Bytes gerechnet zu werden ...

Code Auswählen Erweitern


Monitor:
DISP->HEIZ QUR 8380 Diagnose Erzeuger -  Gesamt Gasenergie:
DC 8A 00 0B 06 3D 05 1A 7C C9 63
HEIZ->DISP ANS 8380 Diagnose Erzeuger -  Gesamt Gasenergie: 30192 kWh
DC 80 0A 10 07 - 05 3D 1A 7C 00 00 01 75 F0 8F 60

Auszug aus Lan_defs
{0x053D1A7C,  CAT_DIAG_ERZEUGER,    VT_ENERGY,        8380,  STR8380,  0,                    NULL,         FL_RONLY,     DEV_ALL}, // Gesamt Gasenergie


Da gibt es doch bestimmt eine Lösung, oder?

Liebe Grüße und Dankeschöns

Eiko

[Schotty]

Da gibt es doch bestimmt eine Lösung, oder?

Yupp, die Lösung heißt freetz 

[AntFleu]

I hadn't seen 8770 to 50. 
So, i checked my two logs days sending to 10000 and never i have a bad temp on 8740.

Otherwise, today i made some new tests
1 - Room sens on C1 and 10001 from BSB during 8 am to midday.
--> No error messages but i have some values at 50 for 8870 every 11 min.
2 - Changing time for 23:15
--> Errors messages back after midnight and of course again some values at 50 for 8870 every 11 min.
3 - Back to the right time
--> Same errors messages and some values at 50 for 8870 every 11 min.
4 - Reset sensors 6201
--> No errors but some values at 50 for 8870 every 11 min.
5 - Waiting two hours and changing time to 23:50
--> Errors messages back after midnight and some values at 50 for 8870 every 11 min.

So, I have an issue only when i send the temperature from BSB-LAN to C2.

6 - I tried to disconnect the power on heat pump for 15 min.
--> Quickly, i have 50 value for 8870.

I come back to that:

Eine Bitte an die Leute, die einen zweiten Heizkreis haben:
Hier ist der Parameter 1000 bisher falsch hinterlegt gewesen, das lässt sich leicht prüfen, indem man per Webinterface die Betriebsart über den Parameter 1000 ändert. Es sollte zwar keine Fehlermeldung kommen, aber die Therme sollte die entsprechende Änderung im Display nicht anzeigen.
Wenn Ihr nun zuerst die Zeile folgendermaßen in der _defs.h ändert:
{0x2E3D0574,  CAT_HK2,              VT_ENUM,          1000,  STR1000,  sizeof(ENUM1000),     ENUM1000,     DEFAULT_FLAG, DEV_ALL}, // [-] - Heizkreis 2 - Betriebsart ***(virtuelle Zeile)***
und dann testen köntnet, ob es dann geht, und danach die Zeile folgendermaßen ändert:
{0x2E3E0574,  CAT_HK2,              VT_ENUM,          1000,  STR1000,  sizeof(ENUM1000),     ENUM1000,     DEFAULT_FLAG, DEV_ALL}, // [-] - Heizkreis 2 - Betriebsart ***(virtuelle Zeile)***
(also nur aus dem "3D" ein "3E" macht)
und dann testet, und es geht erst dann (und vorher nicht), dann wäre das eine sehr wichtige Info. Denn bisher wurde das 2. Byte einer CommandID immer ignoriert. Ich habe jetzt von einem französischen User die Rückmeldung bekommen, dass es nur dann geht, wenn das 2. Byte 3E und nicht wie sonst immer 3D ist. Ich würde das gerne mit Eurer Hilfe überprüfen, ob das ein Einzelfall ist oder ob man das an andern Stellen auch berücksichtigen muss.

Danke und VG, F.

I don't know much but just for information the circuit 2 is not connected directly to the RVS card but on an AVS55.190/127. Certainly always the case but i prefer to indicate it.

I hope it helps.

[Schotty]

Thats really weird and right now I really dont know where the problem could be located besides the controller (or expansion module) itself.
As I said before, basically it works, otherwise you wouldnt be able at all to set the room temp for C2.
But why does the controller sometimes says its 50? And why does that sometimes happen so regularly every 11min? And why it appears to be only after midnight? I really dont know

6 - I tried to disconnect the power on heat pump for 15 min.
--> Quickly, i have 50 value for 8870.

What do you mean with that? The power for the complete heat pump or for the pump of C2?
If you mean the heat pump - I dont really know much about about heat pumps, but I guess you shouldt do that.. 
Besides that, you always wrote 8870 which isnt the room temp and its not even in your complete query - so I guess you meant 8770.
So, if you meant 8770 - how can it reach 50°(?) if you depowered anything? 

But is the "50" really meant as 50°C like I think it is?

Did you try to send /I10001=50 to see what happens?

Good point with the AVS55.190, maybe the error is located there somehow - but I dont know
And as long as we dont have any other user here reporting the same error, right now I dont really see a chance how we could find a reliable solution for this.

About the 3D/3E-stuff I dont know, but if I got it right, that was only about the symbol and had nothing to do with the room temp for C2.

Right now I dont think that its a problem of BSB-LAN, I think its somewhere inside the controller/expansion module. But lets see what freetz thinks about it, he is the coder here

Btw: Because you mentioned a domotic box in your first posting (https://forum.fhem.de/index.php/topic,29762.msg989322.html#msg989322) - how do you usually transmit the BSB-LAN queries and values? Could there be a problem somehow..?

I dont wanna end or brake up the discussion, dont get me wrong, but right now I would suggest to use the wireless room unit for C2 and send the value for C1 via BSB-LAN. If no errors occur, than its fine.
Long term (and believe me, I really dont like to say this right now ) if we cant find any solution: maybe look out for a cheap QAA58 as a second wireless room unit (if you can use two units with one receiver, I dont know). Or -if its possible for you to mount a wired version- get yourself a regular QAA55 for C1, sometimes you can find them pretty cheap.   

[freetz]

@AntFleur und @Schotty: Sorry for not getting back earlier, I have quite a bit of workload to shoulder at the moment and your posts are quite long and complex, so I can't just reply on the subway or so. Just a short feedback: I have no explanation how/why the 50 degrees suddenly appear. It would probably help to figure out what error 65 stands for as this would probably help narrowing down the reason for this error.
And did I get it right that no telegram was sent from the room unit to the heater when you used the QAA for circuit 2? That wouldn't make sense to me.
Unless it is a new/different telegram that I don't know of yet and which could be captured by connecting the QAA to circuit 2 and watch out for the room temperature telegram, there is not much I can think of that I could do to help as I'm way not as well versed in the heaters' behaviours as Schotty is. Regarding Schotty's observations and the errors: On my heater, there is also no error when the room temperature is no longer transmitted. It just goes to "---" and focuses solely on the outside temperature until the next room temperature value is transmitted. My guess is that the 50 degrees is the reason for this strange behaviour, but these must come from somewhere. If they can't be found in the logs (which I haven't checked), then it must be some external factor.

[freetz]

@Luposoft: Hm, das ist seltsam, die Payload besteht aus fünf Bytes (00 00 01 75 F0) und eigentlich sollte die Funktion printDWORD die hinteren vier entsprechend darstellen, da VT_ENERGY als DWord hinterlegt ist. Wenn Du etwas C kannst, könntest Du in der Funktion mal ein paar Debugging-Werte auf dem Seriellen Monitor ausgeben lassen (wie z.B. Serial.println(data_len) um zu schauen, dass die Länge der Payload richtig ermittelt wurde, oder den Wert von lval etc.) Ich kann das leider nicht testen, da ich den Parameter nicht habe...

[Schotty]

And did I get it right that no telegram was sent from the room unit to the heater when you used the QAA for circuit 2? That wouldn't make sense to me.
Unless it is a new/different telegram that I don't know of yet and which could be captured by connecting the QAA to circuit 2 and watch out for the room temperature telegram, ...

Right, thats still a little bit unclear. Fact is, that its this 'special' wireless unit where the receiver is connected to X60 (same one as Jewe has) which doesnt seem to send a lot to the BSB. But because I would think that also this one sends the room temp as an INF-message, I would have thought that at least that one is sent to the bus. But IF it would be a different CoID/telegram than the one we already know, /I10001=xx wouldnt be successful anyway, right? So imho thats not the problem..  

[freetz]

It could be that there is more than one (seemingly) working telegram (for this heater), and that one works 100% and the other one maybe just 90%. Since we have had CommandIDs which behaved perfeclty fine on the webinterface but did not change the value on the heater's parameter, it could also be that the so far known CommandID works but has problems, the same way that the second byte has to be 3E for circuit 2 and not 3D as for everywhere else. But it's just a thought why it would help to figure out what the room controller actually sends...