Yes the blue line is the setpoint temperature of the thermostat. If you have set anticipated start then as soon as the thermostat start to raise the temperature the setpoint raise and the blue line goes up. So it is normal that the blue line goes up before 7:00.
Normally in anticipated heating the thermostat should learn how long it took to reach the desired temperature and next time it will start sooner to try to reach 21 C at 7:00.
Follow it on a longer period to see if it will start sooner.
The blue line start earlier that the point I set on neviweb. The heater start before the blue line⊠i donât understand what the blue line is.
The algorithm must take the outside temperature too.
This morning 18 in the dining room and 21 in the set point. My wife not so happyâŠ
I donât know if the thermostat learn something because they was installed in the end of 2018.
Yesterday I wrote to Sinope technical service. For sure, will keep you in touch! For now, the behavior of the thermostats is not as expected.
The heater start before because the room temperature, the red line, was below the set point, the blue line.
Then the thermostat increase the set point to try to reach the anticipated temperature. But depending on the size of the room, the outside temperature etc, the thermostat donât know how long it will take to reach the new temperature. Maybe SinopĂ© have set a fixed amount of time for the anticipated heating mode. Normally the thermostat should learn how long it take to reach new temperature and adjust its anticipated start time to reach the new temperature on time.
Let me know what Sinopé will tell you.
@claudegel Claude, many thanks for this amazing work. Just started today with HASS.io and your custom components and got my devices to show. One thing I donât understand yet is that my devices are showing in the dashboard but not showing under the devices pick list when Iâm trying to create an automation. Is it possible to use Sinope devices for Automation ?
Yes you can create all automations you want with sinope devices. I have tons of automations running to control everything in my house. I think you want to create automation via the configuration panel -> automations UI and the devices are not showing up in the device list. I donât know why they are not there. Will try to find out.
You can find all your devices in dev tool -> states and it is very easy to manually create automations.
In your config dir create a subdir called «automation»
In configuration.yaml add this:
automation: !include_dir_merge_list automation/
instead of:
automation: !include automation.yaml
leave the file automation.yaml empty with only []. You wonât need this.
In the automation subdir you can add any number of file, xxx.yaml and in each add all the automations you want. The multiple file are usefull to have a clasification of all you automations. Heating, light presence, alerts etc
Let me know if you have trouble creating an automation. Here is a simple one for example
##########################
## turn on christmass light
##########################
- alias: alume noel
initial_state: True
trigger:
platform: sun
event: sunset
offset: "00:30:00"
condition:
condition: state
entity_id: sensor.season
state: 'winter'
action:
service: switch.turn_on
entity_id:
- switch.patio_1
- switch.patio_2
- switch.sinope_technologies_sp2600zb_361e6615_on_off <--- from ZHA for zigbee devices
- switch.neviweb130_switch_prise_sapin <--- from neviweb130 custom_components
- switch.sinope_switch_prise_exterieur <-- from sinope custom_components
The limit is your imagination
1 Like
Hello, I want to share my thinkingâŠ
Because the functionality of the early start is not as expected I decided to improve it by an automation.
In this automation, I now what is the capability of the heater. So I can check the temperature and if it is needed, force the heater to run by setting the hvac to heat.
Here is the long scriptâŠ
# La temperature en chauffage monte d'environ 1,13 degré par heure si la cuisine ou le salon chauffe
alias: "cuisine thermostat amelioration"
trigger:
- platform: time
at: "07:30:00"
value_template: "{{ sensor.dining_room_temp }}"
below: 19.5
- platform: time
at: "07:00:00"
value_template: "{{ sensor.dining_room_temp }}"
below: 19
- platform: time
at: "06:30:00"
value_template: "{{ sensor.dining_room_temp }}"
below: 18.5
- platform: time
at: "06:00:00"
value_template: "{{ sensor.dining_room_temp }}"
below: 18
- platform: time
at: "05:30:00"
value_template: "{{ sensor.dining_room_temp }}"
below: 17.5
condition:
condition: and
conditions:
- condition: state
entity_id: input_boolean.save_electricity
state: 'off'
- condition: state
entity_id: input_boolean.home_presence_state
state: 'on'
action:
- service: climate.set_hvac_mode
entity_id: climate.neviweb_climate_salle_a_manger
data:
hvac_mode: "heat"
- service: climate.set_temperature
entity_id: climate.neviweb_climate_salle_a_manger
data:
temperature: 20
- service: notify.email
data:
title: "Home assistant info"
message: "Demarrage anticipe du chauffage de la cuisine. Trigger: {{trigger.entity_id}}"
- delay: '00:30'
- service: climate.set_hvac_mode
entity_id: climate.neviweb_climate_salle_a_manger
data:
hvac_mode: "auto"
- service: notify.email
data:
title: "Home assistant info"
message: "Chauffage de la cuisine remi en mode auto"
What do you think about ?
Best regards
@BenCour, up to now only the neviweb custom_components can manage two GT125 network. But it coulb be added easily. Write now you can use device.py to get the devices connected to the second GT125. It will create a file in config/.storage called sinope_devices.json.
Start by saving a copy of your sinope_devices.json. Poll your second GT125 network to create the sinope_devices.json file and rename it sinope_devices_2.json. Then restore your original sinope_devices.json for your first GT125 network.
Iâll create a new branch in my git called two-network once I find out how it should be done tonight.
You will have to add some more config in your configuration.yaml. Iâll tell you what to do when Iâm done.
So you have the anticipated heating set to on in Neviweb and with that automation you check if the temperature raise fast enough to reach desired temperature before 08:00 ?
If not you increase set-point to 20oC for 30 minutes and go back to auto hvac_mode after.
Would it be possible to create a sensor that calculate time needed to increase temperature by 1 degree and use it to manage the time we need to pre-heat the room to reach the desired temperature on time.
Yes it will be for chure nice to read the thermostat values in neviweb and find the time to start earlier.
This could be a global solution!
I think it will overcome my capacityâŠ
I will try the automation I just wroteâŠ
Now I am adding a calendar and will start the overheating process for one hour and save energy for a duration selected in the hmi for respecting HydroQuebec plan. Thanks for input_datetime type !
I will keep you informed
Yes instead of over heating for one hour before hydro saving period if we can determine how long it take to raise temperature for each thermostat we can save there too. If it need only 15 minutes to raise temperature to what we need in the morning it is better then raising temperature for one hour before.
@BenCour, Iâve created a new branch «two-network» in my git.
for now only the parameter are working. You will need to add the following parameters to configuration.yaml:
sinope:
server: '192.168.x.163'
server_2: '192.168.x.164' <--- ex.
id: '001EC0C13D21EAAA'
id_2: '111EC0C13D21EBBB' <---
api_key: '50119ec6411bd345'
api_key_2: '00119ec6411bd456' <---
my_city: 'Montreal'
scan_interval: 180
You can add those three parameters but for the other who have only one network they can leave them out. it should work both way.
You can start discorevring your devices on the second network with device.py to create the file sinope_devices_2.json as described before. Donât forget to save a copy of your sinope_devices.json for your first network.
@claudegel Amazing, I will give it a try over the weekend. The 2 gateways are at our cabin up north so I will only get access then.
We know peak periods will only happen when itâs very cold outside. Just benchmark how long it takes to heat your average room, and start your automation in advance by the same amount. The dynamics should remain roughly the same from day to day, assuming you start from the same low temperature.
@vormsty
I personally found out the âearly startâ feature on neviweb to be useless, as it would always start 1h before, even if the room is super-hard to heat. It just never learnt. so I deactivated that feature and put my own time in advance.
Not using Neviweb anymore, so I did my own stuff in HA. I donât have any schedules anymore, HA is reading my alarm in my android phone and starts gently heating 1hr before that, using the heatpump only for energy efficiency purposes. If I wake up without an alarm on my cell, my alarm systemâs motion sensor will pick me up walking downstairs and starts everything full blast. From ~18 to 23 in about 15 minutes. When I go to bed, no schedule, I simply detect when all cell phones are charging. All heating is then turned off at the correct time.
I found schedules to never work for me, they always started either too soon or too late. I was always ending up settings stuff manually, every day. Was annoying. With a little child now itâs just 10 times worse. Automations based on presence/motion is key.
Very interesting!
I am ok that the eary start behaviour is useless: thanks for SynopĂ©âŠ
I trace many curve and know the heater is able to increase more than one degre per hour.
I just made an automation to start heating in heat mode when the the point is below the curveâŠ
I have one point ever 30â starting at 5:30 and ending at 7:30.
I am retired and want to have the temperature at 8:00.
If I wake up earler it is not a problem to have a temperature belowâŠ
It is a lot of work to write automation
For the cold period, I add a calendar and cold time duration variable in the HMI.
All is writted, I just need to testâŠ
Many thanks for sharing your point of viewâŠ
1 Like
BTW, adding motion triggers is not that expensive & itâs easy, just buy a sonoff RF bridge for 20$, a couple of wireless PIR sensor for 5 $ each, and youâve got probably the whole house covered for under 50$. Throw it a couple of door sensors, and you can also pickup when you leave/enter the house.
I already have motion detector for outside lamps.
Itâs a lot of false defections.
For each thermostats I have fiew spare cable and I can / would like to have / motion detection. I would like to have humidity detector to be able to pilot the air exchanger. The brain is the only limit⊠the time tooâŠ
Thierry
I was actually checking on my floor heating theromstat and it appears that early start adapts:
The setpoint is âroom temperature 22°c at 7:30â and the heater is less than 500W so not really fast.
3days ago the temp was 19°c at 4:00 when it started heating and at 7:30 it was 22°c
2days ago the temp was 17.6°c at 4:00 when it started heating and at 7:30 it was 20.5°c
Yesterday the temp was 18°c at 3:16 when it started heating and at 7:30 it was 21°c. (so it basically started one hour earlier)
Today the temp was 19.7°c at 4:25 when it started heating and at 7:30 it was 22°c
Could be that the logic on floor heating thermostat is different from the othersâŠ
Best,
Basicaly the early start is implemented, but is not good as expected.
For me:
I want to have 20C at 8h
It started at 7h21 (temp 17,2) and it was 20 C at 8h46
I am working for implementing an automation to start earler the heating.
I know the capability of the heater is more than 1 degre per hour.
So at 7h30 I must have 19,5
at 7h00 I must have 19
etc.
If the temperature is beloww I change the hvac mode to heat, set the point to 20 for 30 minute and back to auto mode.
Itâs a job to have this automation working.
If you want, i will keep you in touch.
Regards
@vormsty, no problem let me know if you have problem with automation.
@BenCour, today Iâve finished an update to be able to manage two GT125 in the sinope custom_components. Iâll upload it to the new branch «two-network» so anybody who have two GT125 may test it before I merge to master.
It will be available later tonight or tomorrow.