Sinope Line Voltage Thermostats

Bon matin @claudegel.

I’m not much of a coded these days by any means. I pushed your code back through and hit an error around 158 again. My thought is it looks for wattage of one no matter what and produces error when it couldn’t make that connection. I did the following to clear the error:

                    self._wifi_display2 = device_data[ATTR_WIFI_DISPLAY2]
                # removed ATTR_WATTAGE from here and moved to else - line above for reference

                if not self._is_low_voltage and not self._is_wifi_floor:
                    self._wattage = device_data[ATTR_WIFI_WATTAGE]
                else:
                    self.wattage = device_data[ATTR_WATTAGE]
               

OK I’ve corrected the wattage. Please test wifi-support branch

Did you have chances to test the last changes to wifi-support branch ?

Did not yet. I work telecoms and had to run for trouble calls ruining the weekend.

Murphy’s law :grinning:

I’ll give it a go tonight or tomorrow. My 4000w’s will be here sometime next week.

I’ve ordered wall outlet device on Wednesday and received it today. Sinopé have a very fast shipping service. I hope you get them soon. We will add them to HA. Then I will just wait for someone who have low voltage wifi thermostats

Hey guys, I am brand new here.

I just picked up a Sinope TH1300WF, and I am trying to integrate into home assistant. I thought I didn’t need a gateway, am I correct? Already trued Sinope-1 to no avail.

Family is showing as 738-2 if that helps. Thanks!

Welcome to HA
Yes with a wifi thermostat you don’t need a gateway. But you’ve try the wrong custom_component. Sinope-1 is for the miwi devices (GT125). Use the Sinope-130 instead. This one support the zigbee and wifi thermostats. Make sure you add your wifi thermostat in the same Neviweb network than your zigbee devices if you have, or use a new network. Don’t add it to your Neviweb GT125 network.
The TH1300WF is already supported in the Sinope-130 but I’ll merge a new version soon to better support the wifi thermostats. You can try the branch wifi-support for the latest version. If you have other wifi thermostats model, let me know. I need the model number of the other thermostats. For the TH1300WF it’s 738 but I need to find out which model it is for the TH1400WF low voltage wifi and TH1124WF 4000w wifi

This is timely. I have been using the GT125 with my Sinope Thermostats ( TH1120RF-3000) for 5 years now. It appears that my GT125 is shot. It won’t connect to the web. Light for web is not coming on no matter what I try. Am I going to have to get new thermostats or would upgrading to the GT 130 work? From what I read it’s Zigbee and the new devices are all WiFi. Really hoping I don’t need to repurchase all of the units because the hub is out!

You can call Sinopé. They should have some GT125 in stock to honor the warranty of the last GT125 sold. Maybe they can sell one to you.

Unfortunately the GT130 do not connect with the miwi devices of the GT125

Good luck getting customer service from them. Been trying for over a month to get support from them with no response. 15 Zigbee thermostats, all ordered at the same time, shipped with 2 different versions of firmware. Some display the word “Out” under the outside temp, others do not. 3 requests sent in, all have been ignored. I need 3 more thermostats but refusing to order until I at least get a response.

Hey Mike. I just called their support line and they answered right away and helped out. I let them know that I put in a support request about a week ago and it was mentioned that they were away/busy and calling gets a faster response.

I need to try one more troubleshooting step and then it’s off to the sales team to probably replace my GT-125. They do have them in stock for customers needing them.

Hello,
I recently signed for changing the electricity contract.
Now, during the cold season, I will receive a mail telling me the price of kw will be very high next day.
So, I want to save a maximum of electricity during this period, shuting off the watter heater for exemple.
I want to aks you what is the better way to change temporarly the setting point of some thermostats during this period.

Best regards and many thanks for your work !!!

I did the same but instead of getting a lower price for winter and a high price for the peak period I chose the other option. I’ll pay regular price but will be credited 0.50$/kw I’ll save during peak demand. Hydro Québec will send an email before 17:00 the day before they expect a peak period. Those period are from 6 to 9 AM and 16 to 20 PM. I already have a load controler that will cut water heater for those period and another to cut car charger. All my thermostats are Sinopé so I can reduce temperature during peak period but I’ll also raise heating for one hour before each peak period to pre-heat the house especially during the morning. I lower the temperature at night but when there is a peak period at 5 AM I raise temperature and lower it just before the peak. So I’ve created a input_boolean variable like this:

input_boolean:
  avis_hydro:
    name: Avis_hydro
    initial: off
    icon: mdi:signal-variant

in my configuration.yaml. I’ve a button on top of my panel like this

- type: "custom:button-card"
            color_type: card
            color: rgb(223, 255, 97)
            entity: input_boolean.avis_hydro
            icon: mdi:thermometer
            name: Hydro
            state:
              - value: "on"
                color: red
                icon: mdi:alert
                styles:
                  card:
                  - animation: blink 2s ease infinite
              - operator: default
                color: green
                icon: mdi:shield-check
            styles:
            card:
              - font-size: 12px
              - font-weight: bold

each time I activate that button it start an automation that will start or stop many other automations that take care of the following:

  • stop water heater at 6 and start it at 9. stop it at 16 and restart at 20
  • increase temperature of house at 5 and reduce it at 6 until 9
  • repeat the same at 16 to 20
  • stop electric car charging in peak period
  • stop dehumidifier
  • reduce heat pump temperature
  • etc
    for temperature control you just have to create an automation that change setpoint temperature at the time period you want. One to lower temperature and one to increase temperature at the end of peak period.
    The activation of the input_boolean will activate these automations and when the peak period is finish, deactivation of the input_boolean will put everything back to normal.
  - id: pointe active on
    alias: pointe active on
    initial_state: true
    trigger:
      platform: state
      entity_id: input_boolean.avis_hydro
      to: 'on'
    action:
      service: automation.turn_on
      data:
        entity_id: 
          - automation.coupe_courant
          - automation.allume_courant
          - automation.pre_chauffe_thermo
          - automation.pre_chauffe_plainte
          - automation.plainte_off
          - automation.thermo_off
          - automation.plainte_on
          - automation.thermo_on

You do the same with automation.turn_off. You can activate/deactivate peak automations and activate/deactivate normal automations as you wish.
Sinopé is comming with something called Éco Sinopé that will handle that for you. I think it will receive notice from Hydro Québec and set something like the occupancyMode they use to track your cell. this will activate scene etc. to reduce electricity usage

1 Like

Many thanks for your reply.
What I don’t understand is the interraction between time schedule setting point and temporary setting point.
I have many setting points in a time schedule array.
I presume the thermostat (hvac) is in auto mode ? isn’t it ?
Is auto mode corresponding to time schedule ?
Do I change the mode to temporary in cold condition and restore it on auto when the cold period is finish ?
How can I change the mode in an automation script ?
I am confusing also with hvac and preset mode. Can you tell me more explanation about ?

Many thanks for your patience !
Regards
Thierry

Your time schedule is on Neviweb where you have the program for your thermostats.
For your devices you have HVAC mode OFF, MANUAL and AUTO. in AUTO the thermostats will follow the program you’ve set in Neviweb. In manual you will have to change the setpoint manually on the thermostat card or via automation if you want to change temperature.
You also have PRESET mode which are AWAY, BYPASS and NONE.
In AWAY the thermostat will set the temparature you’ve programmed for away in Neviweb for that thermostat. BYPASS is when you are in AUTO or AWAY and you change setpoint manually directly on the thermostat.
For normal condition you can set your thermostats to auto and they will follow the program that you’ve setuped in Neviweb for each thermostat.
For cold condition you can switch to manual (heat) and the thermostat will change to the temperature you have set for manual operation. You can revert to auto when cold condition are finished.
to change that in automation

    action:
      - service: climate.set_hvac_mode
        entity_id: group.sinope_away # you can create a group of thermostats to switch them in one shut
        data:
          hvac_mode: "auto"  # or HEAT or OFF

For preset:

    action:
      - service: climate.set_preset_mode
        entity_id: group.sinope_away
        data:
          preset_mode: "away" # or none

To find more you can check in dev tool, services. each one are described.
If you want more control you can set automation to change setpoint as you which in heat mode

  action:
    - service: climate.set_temperature
        entity_id: climate.salon # or a group of thermostats
        data:
          temperature: 21

a complete automation with trigger, OR condition etc

  - alias: Presence hiver
    initial_state: false
    trigger:
      platform: state
      entity_id: group.personnes
      to: 'home'
    condition:
      condition: or
      conditions:
        - condition: state
          entity_id: sensor.season
          state: 'winter'
        - condition: numeric_state
          entity_id: sensor.dark_sky_temperature
          below: 5.0
    action:
      - service: climate.set_preset_mode
        entity_id: group.sinope_away
        data:
          preset_mode: "none"
      - service: climate.set_temperature
        entity_id: climate.salon
        data:
          temperature: 21
      - service: climate.set_temperature
        entity_id: group.plancher_away
        data:
          temperature: 22

Hope this help

2 Likes

Whaouu ! Cristal clear!!!
Many thanks for your explanation!

I will start to work on tomorrow

Best regards and thanks again
Thi8

Hello,
many thanks for your explanations.
Few questions more…
What is the preset mode “NONE” ?

For setting the HVAC mode to MANUAL I have to write “heat” is that correct ?

So, in cold situation, I have to switch the HVAC mode to manual and after that setting the temperature.

So, if I am correct with that, just the last question:
what’s append if the hvac mode is on “auto” and I set the temperature ?
Is the value in the neviweb is repaced by the new value ?

Sorry for so many questions…

Best regards
Thierry