find your secret key here: Installation · asantaga/wiserHomeAssistantPlatform Wiki · GitHub
Hello new user here, please be gentle! Two days ago I installed the Drayton Wiser kit - a few wrinkles, but got good support from Drayton. Yesterday I got it hooked up with this wonderful integration - many thanks for all the work, it really makes a difference to the usability. And today I’m trying to get clever and make it look pretty! Here’s my first cry for help, and its probably a really simple one…
I want buttons to implement some of the basic Wiser functions such as Boost, Cancel Overrides, etc. The default buttons that came in with the integration are all there and they work fine, but I don’t like to have to press “PRESS”. The standard Button entity that is being used here doesn’t seem to be customisable, so I’m trying Custom-Cards/Button-Card.
It looks ok, but when I click a button it doesn’t work, I get a “Failed to call service” popup.
What am I missing, please?
type: custom:button-card
icon: mdi:water-boiler
name: Toggle
tap_action:
action: call-service
service: button.wiser_toggle_hot_water
Thank you!
Firstly welcome.
The service should be button.press with the entity_id as the button.wiser_toggle_hot_water. Ie
type: custom:button-card
icon: mdi:water-boiler
name: Toggle
tap_action:
action: call-service
service: button.press
data: {}
target:
entity_id: button.wiser_toggle_hot_water
Below is also an example of how to create some of the buttons you mention. I use mushroom cards but you can do similar with others.
- type: custom:stack-in-card
mode: vertical
cards:
- type: custom:mushroom-climate-card
entity: climate.wiser_lounge
name: Heating
show_temperature_control: true
hvac_modes:
- auto
- heat
- 'off'
tap_action:
action: none
hold_action:
action: none
double_tap_action:
action: none
collapsible_controls: false
layout: horizontal
card_mod:
style: |
ha-card {
border-width:0;
}
- type: custom:mushroom-chips-card
chips:
- type: template
content: Boost 1h
tap_action:
action: call-service
service: wiser.boost_heating
data:
time_period: 60
target:
entity_id: climate.wiser_lounge
- type: template
content: Boost 2h
tap_action:
action: call-service
service: wiser.boost_heating
data:
time_period: 120
target:
entity_id: climate.wiser_lounge
- type: template
content: Boost 3h
tap_action:
action: call-service
service: wiser.boost_heating
data:
time_period: 180
target:
entity_id: climate.wiser_lounge
- type: template
content: Cancel
tap_action:
action: call-service
service: wiser.boost_heating
data:
time_period: 0
target:
entity_id: climate.wiser_lounge
alignment: center
card_mod:
style: |
ha-card {
padding: 10px 0;
}
Thank you! Not only have you solved my immediate problem, but you’ve also given me several other ideas to play with. So many options, so little time…
got my OpenTherm Gateway kit, and it’s all linked up to HA, lots and lots of data points., and I have full control over OpenTherm.
heres just some…
Hi! Can I apply multiple set_schedules in the same script? I have tried below but I get an “extra keys” error. Or do I need to set a script per room and then call all the scripts from a single overarching script?
Thanks!
rw_setschedule_a_athome:
alias: RW_SetSchedule_A_AtHome
sequence:
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_living_room
filename: /config/schedules/A_AtHome/A_LivingRoom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_bathroom
filename: /config/schedules/A_AtHome/A_Bathroom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_dining_room
filename: /config/schedules/A_AtHome/A_DiningRoom.yaml
mode: single
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_front_bedroom
filename: /config/schedules/A_AtHome/A_FrontBedroom.yaml
mode: single
Yes you can. I think it might be an issue in your yaml. See how the entity id ahould be formatted.
EDIT: just noticed it is actually your mode line. This should not be in the service call section but just once at the end.
alias: Set away schedules
sequence:
- service: wiser.set_schedule
data:
entity_id: climate.wiser_dining_room
filename: /config/schedules/away/dining.yaml
- service: wiser.set_schedule
data:
entity_id: climate.wiser_lounge
filename: /config/schedules/away/longe.yaml
mode: single
Hey guys!
We’ve got this hub in APAC: https://www.se.com/sg/en/product/CCT501900/wiser-hub/
I can’t seem to be able to get the secret key from the instructions could someone point me in the right direction or will I need to get a US/EU hub?
I have no experience with this hub, that seems to use also special devices
I use successfully this one with the integration https://www.se.com/fr/fr/product/CCT501801/wiser-passerelle-wifi-zigbee-pour-les-appareils-du-système-wiser-génération-2
Hi Mark,
Many thanks! I altered my script to the below but am getting the following error?
Error executing script. Invalid data for call_service at pos 3: extra keys not allowed @ data['mode']
rw_setschedule_a_athome:
alias: RW_SetSchedule_A_AtHome
sequence:
- service: system_log.write
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_living_room
filename: /config/schedules/A_AtHome/A_LivingRoom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_bathroom
filename: /config/schedules/A_AtHome/A_Bathroom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_dining_room
filename: /config/schedules/A_AtHome/A_DiningRoom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_front_bedroom
filename: /config/schedules/A_AtHome/A_FrontBedroom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_front_room
filename: /config/schedules/A_AtHome/A_FrontRoom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_milly_bedroom
filename: /config/schedules/A_AtHome/A_MillyBedroom.yaml
- service: wiser.set_schedule
data:
entity_id:
- climate.wiser_william_bedroom
filename: /config/schedules/A_AtHome/A_WilliamBedroom.yaml
mode: single
Indent your mode line to the same as alias or delete it as mode: single is default anyway.
Thanks - removed it and seems to be working now
Do I have to completely reset my Home Touch? If I do, I will have to re-add all the devices.
@andyblac thanks, I don’t have an OpenTherm thermostat yet but installing it just to get access to OT terminals is an interesting option.
@ndrwha331 yeah, should help you control, as you have it override stat (in your case have it control your boiler)
in HA you get entities for boiler and stat, you just enable for what you want, see below of what I have enabled.
here the HA integration docs
@msp1974 Maybe you are already aware of it, but in case not, is this upcoming change to the climate cards in 2023.9 likely to affect anything in this integration? In particular I was wondering if it would have any impact on Passive Mode.
First you need to see if you have a Wiser Home Touch (the one with the built in LCD display) or the Merten Gateway (without the LCD). If the latter then the method will work, the former then no, it won’t work.
The ‘grinding’ or the noise associated with it is often the valve protection feature. What happens is the iTRV closes the valve completely (the ‘grinding’ is to detect a particular torque to be sure 100% it is closed) then opening to the last stored position. So it may sometimes sound like grinding but Wiser is actually trying to ensure your valves do not get detritus build-up and stick requiring the ‘plumbers trick’ to tap the valve with a spanner or in the worse case replace it.
That gateway will not work with this HA integration. Only the EU Wiser Home or UK Wiser Home gateways will work.
@robertwigley sorry for late reply. I hadnt seen this but think it will be ok. As released yesterday, if you notice anything not compatible with this, let me know and we can review.