Add to the attributes the next switch change. about hasmartthermostat HOT 16 OPEN

Hello, I'm sorry I didn't work on the thermostat for a while, arrival of baby #2 drastically reduced my free time. I hope to be able to make a new build before end of the year (as Christmas gift)

There is a need for a rework of the thermostat attributes because as is, every change in one of the attributes will trigger storing a new state in the database for the thermostat with all the attributes, even those that didn't change. It increases the size of the database and reduces the performance of HA. So I need to change the code to send the PID and debug attributes in some optional sensors that should be enabled or disabled by configuration script.

from hasmartthermostat.

Here you can find the climate.py file that is creating time_to_off and time_to_on as attributes. just overwrite the file that is in the directory /custom_components/smart_thermostat. I suggest anyway to make a copy of the original file in case of problems. climate.py.zip

Thanks, i'll try

from hasmartthermostat.

I've made this change on my own. Let me know if I can post here the updated version of the climate.py

from hasmartthermostat.

@miki3421
Great!!
I am very interested in this feature!

from hasmartthermostat.

Here you can find the climate.py file that is creating time_to_off and time_to_on as attributes.
just overwrite the file that is in the directory /custom_components/smart_thermostat.
I suggest anyway to make a copy of the original file in case of problems.
climate.py.zip

from hasmartthermostat.

Here you can find the climate.py file that is creating time_to_off and time_to_on as attributes. just overwrite the file that is in the directory /custom_components/smart_thermostat. I suggest anyway to make a copy of the original file in case of problems. climate.py.zip

Thanks, i'll try

Let me know if is working or not.

from hasmartthermostat.

@miki3421
@ScratMan

It works well.

It would be better to include this feature in the official version.

from hasmartthermostat.

Guys can you provide some screenshots with this implementation? It would be very interesting to see the actual visuals. Thanks

from hasmartthermostat.

from hasmartthermostat.

I don't see the images... only some tags like [image: image.png]. Thanks

from hasmartthermostat.

from hasmartthermostat.

WOW niceee! Thanks.

Why you did not convert the seconds in the to minutes? :)

from hasmartthermostat.

You can do it. I don't need actually, once is set properly it works very well.

from hasmartthermostat.

from hasmartthermostat.

Which card is the first one? It looks very informative

from hasmartthermostat.

There is a need for a rework of the thermostat attributes because as is, every change in one of the attributes will trigger storing a new state in the database for the thermostat with all the attributes, even those that didn't change. It increases the size of the database and reduces the performance of HA.

I already see that after one week with two smart thermostats... it really slows the system down, and i do not use the stock HA database but MariaDB for the reason the stock db is so slow if you start to pump in data like an own weather station and other trigger intensive stuff.

from hasmartthermostat.