OK for preset mode None it’s when there is no preset mode (kind of preset mode off)
setting hvac to manual is hvac «heat» then you set_temperature to change setpoint temperature
Your thermostat remember three different temperature setting:
away is the temperature you’ve set in the Neviweb configuration for your thermostat.
auto is the temperature the thermostat will follow when it execute the program you have set in Neviweb for that thermostat
heat is the manual setting of setpoint temperature.
Your thermostat will remember both three. if you are in auto mode and you change the setpoint temperature. Your thermostat will go into BYPASS mode (or temporary mode) and at the next step of your auto programmation it will resume to auto temperature.
If you are in auto mode and you switch to heat mode then the thermostat will change to the manual temperature, the last one you’ve set for heat mode and stay there until you switch back to auto mode or away preset.
You won’t change temperature set in Neviweb. Auto program will stay and away temperature will stay as it is set in neviweb.
This way you can have a regular program to control your temperature by setting program in Neviweb and set a manual temperature to let say 18 for hvac heat that you will use when you are in cold period.
Just switch between heat and auto hvac mode.
Have fun and keep asking question if you need
I’m having a strange issue where it sometimes stop updating values in Home assistant.
The solution I found is to restart home Assistant but it would be convenient to find a way to avoid this.
Another point for Sinope thermostat is the anticipation time for the thermal regulation algorithm.
Because I time schedule in fiew thermostat, I see the anticipation time is not suffisant to be at the right value at the right time.
For example I want to be at 21 at 7h30 in the morning and at the evening I set the reference value at 17.
I observe that at 8 o clock the temperature can be 20 or 20,5…
Is that possible to manage PID and anticipation time inside Sinope thermostat ?
In Neviweb there is a parameter for the miwi thermostats called earlystart. With that, the thermostat will learn how long it take to reach the new setpoint and adjust it’s start time to reach desired temperature. But I think that it work only if you use the program set in neviweb for that thermostat. If you change the setpoint to 21 at 7:30 AM via an automation, the thermostat have no idea that the setpoint will change at 7:30 AM. So if you use an automation you will have to validate how long it take to the heater to reach the desired setpoint and adjust your automation to change the setpoint earlier so the room temperature will reach the desired temperature at 7:30AM
Hello Claude,
I use Neviweb, I don’t know Neviweb 130. That is how I fix parameter for thermostats.
For H.A, I use the custom component neviweb.
I change the setting point only in Hydro cold period. So every day is the same schedule and depending of the outside temperature, the real temperature will be late than the time scheduled.
I think the thermostat doesnt learn…
Thanks for your help
In HA you have the choice of three custom component
Sinope-neviweb which is for the miwi devices connected to the GT125
Sinope-Gt125 which is for the same device but with dirct connection to the GT125 to manage them
Sinope-neviweb130 which is for the zigbee devices connected to the GT130 and wifi devices
If you use the first one you can use the program set in Neviweb for your thermostats and the earlystart. I don’t know if Sinopé have set a fix delay to raise the temperature to the desired temperature set in the program or if the devices is actually calculating how long it take to reach that temperature. In that case the thermostat will need few days to calculate the delay it need to reach the desired temperature.
This picture is a screen shot of the history of the thermostat.
I imagine the blue is the setting point and the green.
The red is the real temperature and the green is when the heater run.
You can see the heater start earlier the new setting point but the resulat is bad: the heater has to start much earlier !
in Neviweb for that thermostat did you check parameter «Anticipated start» or «Démarrage anticipé»
In your graph the heating start when you raise the setpoint. It should start before the setpoint changes
Hello,
Thierry anticipated start is checked.
If you look carefully the picture, you can see the green start before the blue. So the heater start before the setting point. It is ok, but a lot to late!
@vormsty what version of HA are you running. In my history graph I don’t have the green fill
I’m gonna set anticipated start in Neviweb to check if I have the same.
Just to be clear, the card is of type: ‘custom:thermostat-card’
I loock carrefuly the curve and the setting on neviweb.
The blue line is not the setting on the thermostat !
For exemple:
At 7:00 o clock: I would like to have 21 C (before, the setting point is 17)
At 3:19 the heater start, the temperature is 16.8 C
At 6:15 the blue line go from 17 to 21
At 7: 15 the real temperature is 17.5 a delta of 3,5 C !
The blue line is not corresponding to the neviweb, nor the anticipating point so I don’t know what is the signification of the blue line.
