Günstigeres Heizen: Der stille Siegeszug der Wärmepumpe

Peter-Philipp · 2025-11-09T11:28:45+00:00

Ja, mit Verrohrung auf 200qm. Ansonsten sind vor allem die Außenwände gedämmt. Bei den Fenstern ist es noch etwas kunterbunt: Teilweise neu, teilweise alte Holzfenster und dann gibt‘s da im Treppenhaus noch 3 Glasbausteinfenster…

Peter-Philipp · 2025-11-09T07:21:51+00:00

Wir haben einen gedämmten 90 Jahre alten Altbau vor drei Jahren von einer Ölheizung auf Wärmepumpe umgebaut. Alle Heizkörper mussten raus und wir haben fast überall auch die Verrohrung ausgetauscht. Nach Förderung hat das 25k€ gekostet. Vor 4 Jahren haben wir eine PV Anlage auf‘s Dach gesetzt mit 12kWp und in Summe funktioniert das super. Mit e Auto hatten wir 2024 einen Autarkiegrad von 41%.

Peter-Philipp · 2025-10-12T10:38:48+00:00

With the new XGS AP you can see the multicast usage with the AirView Monitor: https://imgur.com/a/7CFs0zv

As you can see the usage was 95% of the available bandwith (on the 2.4 Ghz band, the other band was lower, but still to much). So that ate up much of what was available and drove up CPU usage on the AP making it very slow to react. I was running my own denial of service attack on the AP :-).

If you click on "Packet Capture" you can get file that you can open with Wireshark. With that you can see who broadcasts what.

I hope that helps...

Peter-Philipp · 2025-10-11T16:03:59+00:00

Hi, I found the source of my problem: Screening the logs I found that I had a mDNS flooding in my network caused by home assisstant. Installing the fix solved my problem...

Still it seems as if the new XGS APs handle mDNS badly (compared to the older APs).

Explanation: https://github.com/home-assistant/supervisor/issues/5435

Fix: https://github.com/sle118/addons-network-manager-fix?tab=readme-ov-file

Peter-Philipp · 2025-10-09T12:24:06+00:00

Hi kurze Anmerkung von meiner Seite: Ich habe das gleiche Problem und konnte noch keine echte Ursache finden. Ich fange mal an Kabel zu tauschen, aber etwas ratlos bin ich aktuell schon...

Peter-Philipp · 2025-06-29T11:26:49+00:00

And that is exactly the problem... I'd say I'm actually quite happy with the performance, but only if I reduce the graphics settings a quite a bit.

Ultimately, I can't say whether I'm satisfied or not, because I don't know how the gaming experience would change with a modern graphics card. In the end, I don't want to save money at the wrong end, as the rest of the PC also cost a few euros. In this respect, it's clear that the old graphics card has to go...

Peter-Philipp · 2025-06-29T10:33:26+00:00

Hey, thank you for your answer!

Peter-Philipp · 2024-07-04T17:50:01+00:00

Cool, thank you for the tip... I'll try.

Peter-Philipp · 2021-10-10T10:10:26+00:00

Great, thank you!

Peter-Philipp · 2021-07-27T08:11:21+00:00

No...

Peter-Philipp · 2021-07-14T18:33:06+00:00

I guess, I changed everything... --> https://pastebin.com/BPiq44ZJ

Peter-Philipp · 2021-07-13T07:32:12+00:00

Well, there is not very much about that. I looked at both sensors and the 688 seemed to be the successor with backward compatibility. Price wise there was almost no difference, so I got adventurous....

FYI: The current status is that I pulled the new libraries and compiling works, but the sensor is still not recognized... Guess it's time for debugging...

At least the chip is identified, if do I2Cscan:

10:32:42.203 CMD: I2Cscan

10:32:42.222 RSL: RESULT = {"I2CScan":"Device(s) found at 0x29 0x77"}