datenhamster

joined 2 years ago
[–] datenhamster@feddit.org 1 points 2 weeks ago

https://oneuppuzzle.com/ I finished the puzzle #646 (8x8) in 4 minutes, 41 seconds in One Up Puzzle.

[–] datenhamster@feddit.org 2 points 3 months ago

Unsere Regierung würde das so formulieren: Die Anreize zum Kauf eines Verbrenners sind nicht hoch genug.

[–] datenhamster@feddit.org 9 points 6 months ago (1 children)

I am 190cm and got a Brompton C-Line with Telescopic Seatpost. The seller recommended it for my size - i use 5 cm of it.

[–] datenhamster@feddit.org 6 points 6 months ago

Habe Tibber. Eine Person tagsüber zu Hause. E-Auto. Beste Wahl bisher. Habe gerade mal bei Check24 geguckt. Komme mit Festpreis in Hamburg aktuell auf 34 Cent. Unser Nutzungsprofil bei Tibber ca. 27 Cent im Schnitt. Ginge günstiger, wenn wir zu billigeren Zeiten vorkochen würden. Um eine App wirste vermutlich nicht rum kommen.

[–] datenhamster@feddit.org 3 points 6 months ago

Genau das. Für mich liest sich der Artikel so, als müsste möglichst oft Lichtbilck drin stehen. Normalerweise habe ich einen EnBW-Vertrag, war aber letztens in einer Gegend ohne EnBW. Konnte an Ladesäulen parken ohne Parkgebühren (muss man also rausrechnen) und teilweise AdHoc-Laden für 49 Cent bei 50 kW

[–] datenhamster@feddit.org 6 points 9 months ago (1 children)

I have exactly this laptop - with 96 GB RAM. It is really as good as described.

[–] datenhamster@feddit.org 9 points 10 months ago

Just bought an Tuxedo InfinityBook. Very nice piece of hardware.

[–] datenhamster@feddit.org 9 points 10 months ago

Na schön, mehr Sendezeit für Alitsches Lügen.

[–] datenhamster@feddit.org 1 points 11 months ago

Ok, now I know why. without the +1 the automation does not trigger when the temperature is over the target and the TRVs running on idle. The +1 triggers the automation and switches them off until the room temperature is under the target temperature. So it does not explain why the mode is switched from heat to off or the other way around in the target +1° range.

[–] datenhamster@feddit.org 1 points 11 months ago

Thank you. I will look at it

[–] datenhamster@feddit.org 1 points 11 months ago (1 children)

I was young and... I don't know why I used it a few years ago. I will try your suggestion.

[–] datenhamster@feddit.org 1 points 11 months ago (3 children)

I use the generic thermostat but I want to switch the TRVs to different temperatures/states depending on a schedule and if we are at home or not. The automation changed over the last 3 or 4 years but basicly it was one of my first experiments with HA. It worked flawless and did what it should.

Maybe it's not the best or refined but it worked.

triggers:
  - entity_id:
      - sensor.wohnzimmer_temp
    trigger: state
conditions:
  - condition: and
    conditions:
      - condition: state
        state: "off"
        entity_id: binary_sensor.balkontur_contact
      - condition: state
        entity_id: input_boolean.wohnzimmer_heizung
        state: "on"
      - condition: template
        value_template: >-
          {% if states('input_boolean.away_mode')=='off' %} {% if
          states('schedule.testkalender')=='on' %} {{
          states('sensor.wohnzimmer_temp') | float <
          states('input_number.wohnzimmer_temperatur_tag') | float + 1 }} {%
          else %} {{ states('sensor.wohnzimmer_temp') | float <
          states('input_number.wohnzimmer_temperatur_nacht') | float + 1 }} {%
          endif %} {% else %} {{ (states('sensor.wohnzimmer_temp') | float) |
          round  < states('input_number.temperatur_away_mode') | float + 1 }} {%
          endif %}
        enabled: true
actions:
  - action: climate.set_temperature
    target:
      entity_id: climate.heizung_wohnzimmer
    data:
      temperature: |
        {% if states('schedule.testkalender')=='on' %}
          {{ states('input_number.wohnzimmer_temperatur_tag') | int + states('input_number.wohnzimmer_heizung_offset') | int }}
        {% else %}
          {{ states('input_number.wohnzimmer_temperatur_nacht') | int }}
        {% endif %}
      hvac_mode: |
        {% if states('input_boolean.away_mode')=='off' %}
          {% if states('schedule.testkalender')=='on' %}
            {% if states('sensor.wohnzimmer_temp') | float < states('input_number.wohnzimmer_temperatur_tag') | float %}
              heat
            {% else %}
              off
            {% endif %}
          {% else %}
            {% if states('sensor.wohnzimmer_temp') | float < states('input_number.wohnzimmer_temperatur_nacht') | float %}
              heat
            {% else %}
              off
            {% endif %}
          {% endif %}
        {% else %}
          {% if states('sensor.wohnzimmer_temp') | float < states('input_number.temperatur_away_mode') | float %}
            heat
          {% else %}
            off
          {% endif %}
        {% endif %}       
mode: single

 

Hi guys. Got some curious behavior.

HA (automation) switches the TRV from off to heat to off to heat...

As I changed the TRVs (Bosch to Sonoff) a few days before, I first thought, it is the new one. Looking through the logs, it also happened with the old one. I am not sure, but it looks like it happens since the last HA Update. Currently running 2025.1.4.

The automation checks on every room-temperature change if it is over or under the target temp. It switches from heat to off after the room has reached the target and switches from off to heat if the temp is under the target.

For example a is 20°C, it happens between 20°C and 21°C. If the setting is heat and the temperature is between 20 and 21 the TRV is switched to off or the other way, if it is on off. I tried to round the temp, but this does not change the behavior. It is always switching to the other setting in this 1°C range. If the room temperature in this example is over 21°C it stays off. Under 20°C it stays on heat.

I never noticed this before, so I think something has changed with 2025.1 but I don't know what and can't find a solution.

Maybe somebody can point me in the right direction to find the error.

view more: next ›