Not necessarily. The "current state" is saved based on a report received from the device itself. The "state variables" are created and saved by the developer of the driver based on some logic, at some point in time. Also, the state variables persist if you change drivers, so the value of 69.50 that you see, may have been saved long time ago, and its value may not even be related to the current driver.
Thanks, @bobbyD that's helpful. In follow-up, does the state variable have any bearing on Brawl manager function or thermostat control or function?
I discovered this when I was trying to set up thermostat controller in preparation for warmer weather. I added the sensor since it’s in a bathroom on the top floor and just wanna make sure it’s not skewing the average temperature from all of the sensors.
Is it possible to confirm that only the current state temperature is used in thermostat controller logic as well as rule machine logic?
Also, is there anything I can do to correct the state variable number or is that even necessary? My OCD brain is not gonna let it go!
Apparently, developer's OCD brain had a reason to save the "reported value" in a variable for some reason. Depending on what driver you are using, the developer who created it, can provide an explanation why that value was important to be saved and posted on the Device Details page.
Just IMO as a developer of a bunch of drivers... I often save many things the device reports to Current States but not as State Variables if I am not sure there is a demand/value for the information. Some things provide a TON of info that nobody cares about.
But, it is sometimes useful to have some of it displayed somewhere in case someone sees it and goes "I need that...". Then I can rev the driver and have it added as a State Variable. I also generally save anything I put as a State Variable in the current states so I can compare new data readily and decide if I need to pop an event because it changed (or not).