I’m pretty new to HA. I’ve set it up and I keep editing the confirmation and everytime I restart to apply the changes, all the switches, sensors and even the thermostat lose their values. The most annoying is the thermostat (classic thermostat entity) because I have to turn it on selecting heat/cool and set the temperature. Is there a way to keep all these values across restarts?

Edit: I’m using HA OS on Proxmox. All the sensors and switches slowly goes back to “normal” as soon as they publish their state, apart from some entities that have values provided by HA itself and not by the devices (like the thermostat).

  • peregus@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    All the devices (sensors and switches )sends their status via MQTT; I’ve manually configured them all via yaml. The problem is in HA itself since as soon as I reload the config, the thermostat (which is a HA entity by itself), loses the setpoint and the status (heater/cool/off).

      • peregus@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        For MQTT that’s the retain flag, but for HA I don’t know what that is and I really need it!!!

        • DeltaTangoLima@reddrefuge.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          8 months ago

          The retained flag simply tells the MQTT broker to keep the last message published for that topic, so it’s always available (rather than timing out and emptying the topic).

          Like I said, you should probably do a packet capture to see what’s happening when HA queries states (either from devices or MQTT - it doesn’t matter).

          • peregus@lemmy.worldOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            8 months ago

            HA doesn’t query any state. The thermostat is within HA, it doesn’t have to query anything from anything, that’s what I’m investigating. The setpoint is set in HA and HA retains that number.

            • DeltaTangoLima@reddrefuge.com
              link
              fedilink
              English
              arrow-up
              1
              arrow-down
              1
              ·
              8 months ago

              That doesn’t make sense. HA doesn’t “own” the setpoint - the physical thermostat does. All HA is doing is telling the thermostat what setpoint to use, as if you were standing in front of the thermostat yourself.

              What thermostat are you using?

                • DeltaTangoLima@reddrefuge.com
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  arrow-down
                  1
                  ·
                  8 months ago

                  Ah, so your real issue is just the thermostat? Your OP made it sound like you were asking about all switches and sensors.

                  Is it just the setpoint that you’re losing and not getting back after restart? I’m assuming it’s getting the current temp back from the sensor just fine?

                  • peregus@lemmy.worldOP
                    link
                    fedilink
                    English
                    arrow-up
                    1
                    ·
                    8 months ago

                    No, my problem is not just the thermostat! All the sensors and switches loses their state, but while they get them back in a while kapart from the battery powered sensors), the thermostat has to be set back manually.