Python Plugin: Smart Virtual Thermostat

[drak]

I have one concern regarding SVT.
When i update thermostat target, so it is higher than current temperature, the SVT correctly turns on the heater. However i set calculation cycle to 80 and i noticed that heater is on 40 minutes, and there is 40 minute pause event if the temperature is far from target. Then o had the cycle set to 60, it was same, half time heating (30 minutes), half time pause. I would expect that the heater would stay on until the target temperature is reached. Im i wrong ?

Regards
Piotr

[jake]

I have one concern regarding SVT.
When i update thermostat target, so it is higher than current temperature, the SVT correctly turns on the heater. However i set calculation cycle to 80 and i noticed that heater is on 40 minutes, and there is 40 minute pause event if the temperature is far from target. Then o had the cycle set to 60, it was same, half time heating (30 minutes), half time pause. I would expect that the heater would stay on until the target temperature is reached. Im i wrong ?

Regards
Piotr

Have you set a minimum time per heating cycle? The 30 minutes per 60 minutes will prevent overshoot.
How long do you have SVT running? The system might need more cycles to define the thermal properties of the room.

When the system in my case need to stop the cool down of the room at night (we use a fire place in the evening), i always see 15 minute heated cycles per 60 minutes) this takes perfectly care of ramping down the temperature to the setpoint and stay there within 0.1 degrees, even with floor heating. Recently I tuned up the setpoint by 2 degrees, SVT was immediately on for 40 minutes and hit the target half an hour later.

[Logread]

I have one concern regarding SVT.
When i update thermostat target, so it is higher than current temperature, the SVT correctly turns on the heater. However i set calculation cycle to 80 and i noticed that heater is on 40 minutes, and there is 40 minute pause event if the temperature is far from target. Then o had the cycle set to 60, it was same, half time heating (30 minutes), half time pause. I would expect that the heater would stay on until the target temperature is reached. Im i wrong ?

Regards
Piotr

Have you set a minimum time per heating cycle? The 30 minutes per 60 minutes will prevent overshoot.
How long do you have SVT running? The system might need more cycles to define the thermal properties of the room.

When the system in my case need to stop the cool down of the room at night (we use a fire place in the evening), i always see 15 minute heated cycles per 60 minutes) this takes perfectly care of ramping down the temperature to the setpoint and stay there within 0.1 degrees, even with floor heating. Recently I tuned up the setpoint by 2 degrees, SVT was immediately on for 40 minutes and hit the target half an hour later.

Thanks @jake. I’d like to flag that the logic of the SVT is different from a hysterisis thermostat. Heating is not based on current temperature being lower than set-point but rather on the quantity of energy needed in a time interval to achieve a given temperature over cycles.
And this requires several days of learning for a given set up. Patience and proper tweaking is key.

[EmKaRo]

How can you reset termostat, as I had a few days of trials and tests, so I can have just "working" expireince ?

[Logread]

How can you reset termostat, as I had a few days of trials and tests, so I can have just "working" expireince ?

Just delete the user variable associated with the plugin. If I am not mistaken this is explained in the wiki

[renerene]

Hello developers,

This is my second year my house is heated with SVT and I really like it. Just one thing....

At the moment I have to manually calculate my switch-on time in the morning, between 4 and 6 am to have the house warm at 7.
It would be great to have some kind of dummy device, that represents a warm-up time, or even better, the time in the future in which the temp is 'normal', if you switch from economy to normal now. The last option saves me the trouble of time calculations. If targetTime >= '7:00 am' then switch to normal

I guess the current software has better knowledge and algorithms to calculate these times, compared to my self made script.

[EmKaRo]

How can you reset termostat, as I had a few days of trials and tests, so I can have just "working" expireince ?

Just delete the user variable associated with the plugin. If I am not mistaken this is explained in the wiki

Thanks, indeed it was in the wiki.
One more question, my thermostat is updated every minute, is it possible to change this time, as my termometr update's every 10 seconds, this 50+ seconds of heating causes temp going to high.

[bimedana]

yes, in last version is perfectly right!

[alarm_guy1]

Hi guys, been using SVT for quite a while now and it has been perfect, however I recently did an update to the latest version and it has gone to pot, the heating seems to be constantly on.

I have a blockly setup for timers so it un-pauses the SVT at certain times of day as we are out working, this had worked fine on the previous version.

now since the update, it is either freezing or boiling, it is mid winter here and i'm in my underwear, contemplating if Speedos are acceptable this time of year.

Can I uninstall and go back to the previous version?
or what are my options.
The current bonus is we can now use the Gas meter needle as a fan,

Cheers

[Logread]

Hi guys, been using SVT for quite a while now and it has been perfect, however I recently did an update to the latest version and it has gone to pot, the heating seems to be constantly on.
Can I uninstall and go back to the previous version?

Did you update the plugin, domoticz, or both ?
If it is the plugin or both, the last two updates of the plugin introduced only cosmetic changes (but I do not known which version you jumped from). Did you try deleting the user variable associated with the plugin and restart ? This should kill all the learning in case some heating parameters went wrong.

Otherwide, did you try disabling the blockly / timers ?

In any case, if the above does not work, please run the plugin in debug mode and send me the log by pm (pls do not post here to avoid clogging the thread).

[alarm_guy1]

Hi thanks for the quick response.

I literally only updated the SVT but no idea from what version TBH.


just deleted user variable..

so will see how that goes.

manythanks

[Logread]

A breaking change was introduced in domoticz from version 4.10298 that effects the creation of user variables via the domoticz API, that the plugin uses to store learning data.

Github user @informagico has kindly updated the plugin code accordingly. Many thanks to him.

Please update your plugin to the latest version if you are upgrading domoticz to a recent beta !

[alarm_guy1]

Any help with this error:

cheers

sudo git pull --force
Updating 3088c35..73adbb2
error: Your local changes to the following files would be overwritten by merge:
plugin.py
Please commit your changes or stash them before you merge.
Aborting

[Logread]

Any help with this error:

cheers

sudo git pull --force
Updating 3088c35..73adbb2
error: Your local changes to the following files would be overwritten by merge:
plugin.py
Please commit your changes or stash them before you merge.
Aborting

You made changes to the local copy of the plugin... so to protect these, the git software does not overwrite. You need to decide if you want to keep these or otherwise the simplest if you are not familiar with git is to delete the plugin folder and proceed like a fresh install.

[alarm_guy1]

Cheers, i am now just testing, but initial results look promising

cheers

[alarm_guy1]

Hi Me again,

just trying in Blockly to swap between Normal and Economy, at certain times.

i.e. 22:00 swap to Economy and at 05:45 swap to Normal.

but it doesnt seem to swap.

keith

[Logread]

Hi Me again,

just trying in Blockly to swap between Normal and Economy, at certain times.

i.e. 22:00 swap to Economy and at 05:45 swap to Normal.

but it doesnt seem to swap.

keith

Did you try timers or lua ? I am using timers. I never used blockly so not sure about the logic, but I am almost sure this is not related to the plugin. Could rather be the broader python plugin devices vs the event system ? I remember reading about this but cannot remember where. You may want to search the forum a bit ?

[alarm_guy1]

cool i will give it a try

[alarm_guy1]

Cheers,

all working now

many thanks

[EmKaRo]

Is it possibile to avoid few second on/off triggers like below?

2018-12-27 19:01:01.384 Status: User: Admin initiated a switch command (14/Piec dół/On)
2018-12-27 19:01:02.956 (Piec) Light/Switch (Piec dół)
2018-12-27 19:01:02.947 Status: User: Admin initiated a switch command (14/Piec dół/Off)
2018-12-27 19:04:01.110 Status: User: Admin initiated a switch command (14/Piec dół/On)
2018-12-27 19:04:06.895 (Piec) Light/Switch (Piec dół)
2018-12-27 19:04:06.888 Status: User: Admin initiated a switch command (14/Piec dół/Off)