I was just being picky, don’t mind me. I will keep it the way it is… Now, I upgraded to core-2021.12.9 and guess what, I have to copy switch.py again, will do that next. It was probably not merged in yet.
Thanks
Stéphane
Hello Claudegel,
I need your guidance to configure my Sinope with home assistant, I try to understand from Github,
As I am a mechanical designers, I have very very basic knowledge in coding. I am trying to understand the Github details but all is over my head. if you have some time can i contact you through email.
Regards
Vinod
Stéphane, see post #928. New easier way of loading custom quirks that is unaffected by core updates.
Ça va te faciliter la vie pas mal 
Please open an issue in Github for the custom_component you want to install and I’ll guide you for the installation. Pick any of the three component that match the one you want to install and click on issues button then open a new issue.
choose between sinope-1, sinope-130 and sinope-gt125 then open an issue and i’ll guide you
I’ve update my automation to set automatically the peak mode upon reception of Hydro email.
I’ve found out that if a DR period last more then a day, the sensors sensor.wintercredit6_9h and
sensor.wintercredit16_20h are not set to 0 after the DR period and stay at there old value. This way it will work if a new DR email come in for morning, evening or both.
###############################################
stop mode peak when there is no peak for the next morning period
###############################################
- id: stop morning peak
alias: stop morning peak
initial_state: true
trigger:
platform: time
at:
- "20:16:00"
condition:
condition: template
value_template: >
{{ states('sensor.wintercredit6_9h') < states('sensor.today_number') }}
action:
service: input_boolean.turn_off
entity_id: input_boolean.avis_hydro
###############################################
# stop mode peak when there is no peak for the next evening period
###############################################
- id: stop evening peak
alias: stop evening peak
initial_state: true
trigger:
platform: time
at:
- "20:15:00"
condition:
condition: template
value_template: >
{{ states('sensor.wintercredit16_20h') < states('sensor.today_number') }}
action:
service: input_boolean.turn_off
entity_id: input_boolean.avis_hydro_soir
2 Likes
Doesn anyone else have issue that EcoSinope is not in sync with Hydro-Quebec peak period ?
Also, sinope only start heat 15 minutes after, instead of at the end as it was before.
I was using the ecosinope in the application. (the email is set to my gf account and I don’t want to get into changing the email account for this yet …)
On saturday and Sunday, I didn’t get any warning or anything in their application and my thermostat didn’t change unless I manually did.
I am thinking of adding a custom automation in HA for her to add the period for the next peak. But I won’t know if there is change.
I think that Sinopé is working on there server. Yesterday I got disconnected on my GT130. No internet connection to Neviweb because they changed the port number for the GT130 to talk to Neviweb. I had to open all port on my firewall instead of just port #4544 and 4553. Once connected the response delay to change devices state or temperature was a lot shorter then before. A lot better.
As I catch directly the Hydro email to trun on turn off my system I’ve noticed before the cut that my devices on Éco Sinopé was activated or deactivated around 10 to 15 minute later then the DR start and stop. I hope they are working on that to improve Éco Sinopé reaction time.
This morning Neviweb switched on my thermostat at 9:11 and my load controller for water heater at 9:15
Could it be a good thing as to not power on everything at 9:00 to protect our electrical system from excessive demand. If you have an old house maybe it is better to turn on gradually instead of turning everything on at once. But at the beginnig of the DR period it should cut everything at 6:00 or 16:00
As to monitor the hydro email with imap-email-content you can monitor your gf account directly. Imap-email-content will only look for email comming from [email protected]
Hi all,
Anyone was able to link a sw2500zb wall switch using the ConBee II?
I have 3 of them and i cannot not get them to connect to the zigbee controller.
SW2500ZB are supported by ZHA. I’ve many switch and dimmer on Conbee II.
Can you provide some log ?
Add this in you configuration.yaml file and restart HA then try to connect your switch
logger:
default: warning
logs:
homeassistant.components.zha: debug
zigpy.application: debug
When I press the 2 buttons at the same time, after a few second I get the blinking red light.
Added the logger in the configuration.yaml, restarted HA but nothing shows up in the logs.
You should go in configuration->device and services. Open Conbee II card and click the blue button add device. Then press the two button on your switch starting from the one that is the closer to the Conbee II.
When the indicator light flashes red, the switch or dimmer is trying to connect to the network, but no gateway is detected. Make sure the gateway is properly plugged in and a connectivity session is enabled.
If the problem persists, the device might be located too far from your Conbee II. If necessary, bring the gateway closer to your device or add a compatible product that can serve as a signal repeater between the gateway and the device you want to connect.
Just got and installed a TH1300ZB today. Took a few re-pairings but seems like it’s working now.
I am used to Zwave devices but I did expect to be able to configure the device in HA. I am using ZHA.
Reading this thread and playing around in the Clusters I can see the values but will this ever be able to be edited in a more human readable manner?
For example, I’d like to switch to 12hour which I thought would be a toggle but am not seeing that one. Found some documentation showing the attribute at 0x0114 but can’t find a cluster containing that.
Is this normal for Zigbee or am I missing something?
Quirk: zhaquirks.sinope.thermostat.SinopeTH1300ZB
Appreciate all your help in this thread @claudegel . I definitely haven’t read all 950+ posts but looks like you’ve contributed to this a lot.
I already have 2 TH1124ZB and one SP2610ZB connected to the Conbee II and a Aqara door sensor.
I tried to connect the wall switch be being right next to the Conbee to see if the distance was a factor and i get the same result.
I am not sure my smartenergy_metering summation_delivered sensor value is updating but even if it isn’t, is there an explanation somewhere of what these mean? Just starting to get into the energy monitoring aspect so forgive my ignorance.
Is it total since installed?
If so, would I need to create a sensors for hourly, daily, monthly, etc usage?
Looks like for the Time Format it should be 0x0114 under 0xFF01
if(TimeFormatParam == “12h AM/PM”){//12h AM/PM
traceEvent(settings.logFilter,“Set to 12h AM/PM”,settings.trace)
cmds += zigbee.writeAttribute(0xFF01, 0x0114, 0x30, 0x0001)
}
else{//24h
traceEvent(settings.logFilter,“Set to 24h”,settings.trace)
cmds += zigbee.writeAttribute(0xFF01, 0x0114, 0x30, 0x0000)
Trying that in HA gives me an “276 is not a valid attribute id” error though
How does one get an attribute added to a cluster?
Sorry for all the replies - posting as I am experimenting/researching and that’s making noise I know.
@claudegel - am I reading it right that you just added this attribute to the zha code 7 hours ago?! 
The flashing red light is because the SW2500ZB don’t see any zigbee gateway. Either you Conbee II doen’t go in discovery mode or there is something you miss.
First put you Conbee II in discovery mode. Then press the two button on your switch. It should pair in few seconds.
Open your ZHA module and look for Zigbee Coordinator in devices list. In that click on add devices via this device. It should open the discovery window and wait for your SW2500ZB to show up
Yes I’ve done a PR that was just merged in dev branch today. It should show up in next ZHA release. I hope it will be in next HA update. If you want to test it faster then see post #928 that explain how to add custom quirks without overwriting ZHA.
1 Like
Ok merci. Je vais voir si switch.py est intégré au prochain update, sinon, je vais suivre ta recommendation. Merci!