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.
Hello,
Thanks for your latest post.
In neviweb, can you explain me the difference bettwen “hors gel” and 5 C ?
Is that possible to put the hvac mode in “hors gel” ?
Hello,
I have a problem with input_datetime
I declared a date time in configuration.yaml with time and no date.
This is for the cold period duration.
In developpement tool, template editor I can enter:
delay: {{states(‘input_datetime.coldperiodeduration’)}}
and the tool write the value selected in the hmi.
in automation it is an error:
action:
- …
- delay: {{states(‘input_datetime.coldperiodeduration’)}}
Error loading /config/configuration.yaml: invalid key: “OrderedDict([(“states(‘input_datetime.coldperiodeduration’)”, None)])”
in “/config/automations/coldperiod.yaml”, line 36, column 0
Can you correct me the syntax please ?
Hi, for «hors gel» it is the equivalent to 5oC. Sinopé just put a name on a specific setpoint setting. When you select «hors gel» the thermostat goes to 5oC automatically to protect from freezing. In HA you can have an automation that will do the same plus an allarm if temperature goes below 5oC
hi @vormsty, In your configuration.yaml do you have the following
automation: !include_dir_merge_list automation/
In your error message you have /config/automations with an «s» at the end.
is it the same in configuration.yaml ?
For those hwo have two GT125, I’ve added the possibility to configure both in device.py which will create the configuration file for both GT125 and add devices in each.
Please test it on https://github.com/claudegel/sinope-gt125/tree/two-network
Yes a have a folder for all automations.
I have for each automation one file.
The folder name is automations
And in configuration.yaml do you have
automation: !include_dir_merge_list automations/ with an «s» at the end
@vormsty, sensor time_date with option time give you the hour.
delay is looking for a time period not hour. Like wait 4 hour, delay: “04:00:00”
On my side I have one automation that stop water heater at 6 am and another that start it at 9 am.
If you want you can have a delay: “03:00:00” between stop water heater and start water heater
For anyone following, I did receive a response from support. They advised me that the GT130 gateway was required for the firmware upgrade and by connecting the thermostats to the GT130 they would update their firmware automatically. GREAT! So I ordered up the 3 more thermostats I needed to finish the house and the GT130 as well.
It arrived last night, so I quickly moved the kitchen thermostat and storage room thermostat over to the GT130. At some point overnight, they did update. But not the firmware. They received a software update, so now both my kitchen thermostat and storage room thermostat are on software version 0.6.4. But my kitchen thermostat is still on firmware version 1723, my storage room thermostat is on version 1573, and my new ones are on version 2007.
At the end of all of this, I’m still left with 11 out of now 18 thermostats that do not display “Out” underneath the outside temperature. 15 of these 18 were purchased directly from Sinope at the same time so I would expect the same functionality out of all of them. I would also expect support to give correct information. At $105 each taxes inc x 18 thermostats, these thermostats are by far the largest single investment in my smarthome. To say I’m disappointed in Sinope right now would be an understatement.
Hi here is what I have
TH1300ZB on GT130 software 1.0.9, hardware 0
TH1300ZB on ZHA software 1.0.9, hardware 0
TH1120RF on GT125 software 1.3.9, hardware 0
TH1120RF-3000 on GT125 software 1.7.0, hardware 1
TH1120RF-4000 on GT125 software 1.7.0, hardware 1
I’ve many of each and each of the same model are at the same version. Both GT125 and GT130 have been updated somewhere in last few month. The TH1300ZB on ZHA is the last one I got so this one came at that version.
IMO, there is just no way that the early start feature can work properly. Yes, the time required to heat up a room is dependant on the current temperature; something the thermostat can figure out on its own after some time. However, it is also very dependant on the outside temperature, as losses are much greater when it’s cold outside. That, I believe, there’s no way for Sinope to figure this out.
Think about it; does it make sense for a room to take the same time to heat when room temp is at 18c, while you’re asking for 22c, when it is 18c outside versus when it is -20c outside? Of course not. Is it simple for a thermostat to figure this out? Of course not.
If you implement such as large delay, you should also look at " AUTOMATION MODES", as there’s a bigger chance the automation can/will run while it’s not finished from the previous call.
Im getting the following error
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/helpers/entity_platform.py”, line 197, in _async_setup_platform
await asyncio.shield(task)
File “/usr/local/lib/python3.8/concurrent/futures/thread.py”, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File “/config/custom_components/sinope/switch.py”, line 59, in setup_platform
devices.append(SinopeSwitch(data, device_id, device_name, device_type, server))
UnboundLocalError: local variable ‘server’ referenced before assignment
Sorry I forgot one server assignment
I’ve updated the branch to fix it
put server = 1 at line 59, just before devices.append(S…
or just download switch.py
I hate to ask this, but since there are so many users on here that are technical you might be my only hope. My GT-125 was not connecting to the web so I went through troubleshooting on my own and with Sinope’s support. It was determined that my unit was out of warranty and I was sent to the sales team to buy a new GT-125. I received my new one today and lo and behold I am having the EXACT same issue. Web light does not go green.
I have tried:
- A different ethernet cable and power outlet
- A different port on the switch
- Direct connect to my modem - bypassing the entire router/hub
- Crying
At the basics of things, one of those would have gotten some sort of different outcome, but both devices are behaving the exact same way. I don’t know that I’ve experience this before and it’s making me think it’s environment specific, but I can’t determine what would all of a sudden cause the same type of device to not work!