Anyone has any pointers?
I guess I can build something to export the logs and visualise them, but was hoping there is a more straightforward alternative.
This is a (new) feature request. It wouldn’t be very hard to implement, at all.
I am refactoring this integration at the moment - I will try to add it in in the next few weeks, as an extra_state_attr…
Maybe also a get_schedule service call, and a set_schedule service call…
It this feature does not appear in (say) two months - submit an issue on github, and it will prompt me to action - or PM me.
All,
I have a RPI4 running homeassistent image installed with the raspberry imager. I’m new to homeassistent
I’m trying to integrate the honeywell Evohome but whatever I try I don’t get anything in homeassistant home page, but also no error message in the log file.
The password and email address are 100% correct as I can login on the honeywell website and see the system.
Here is my configuration.yaml
# Honeywell Evohome
evohome:
username: [email protected]
password: xxxxxxx
location_idx: 0
scan_interval: 60
logger:
logs:
custom_components.evohome: debug
custom_components.climate.evohome: debug
Try:
evohome:
username: [email protected]
password: xxxxxxx
logger:
logs:
homeassistant.components.evohome: debug
homeassistant.components.climate.evohome: debug
evohomeasync2: info
evohomeasync2.broker: warning
Some passwords (i.e. some special characters) that work via the website, do not work via the RESTful API.
Hi all, I have the honeywell evohome integration working - thank you - just a stupid question: how do I setup automations and use buttons in my house to set a certain temperature? Do you have an example script?
To set temps for a zone you just set up a thermostat card with the relevate climate.Lounge (or whatever) and you get this:
If you want to set automations you use the same climate.relevantzone. But be careful as you’ll need to ensure the automations dont mess up your existing schedules in Evohome (if you have any).
Dont needs scripts as such to do the basic stuff you mention.
Thanks @davidtja
This is what I have now:
So what I currently do is manualy press + until the room is 20C. Then later lower it to 16c when I want it to turn off.
What i want to do is create shortcuts/buttons to set temp to 20C with a single click. Do I need a script? Automation? And how does this impact the programming of evohome (which is set to change temp at 18.00 for example to 20C).
1 Like
If you want similar to my example (rather than press + or -) you need to use the basic thermostat card in lovelace, what you have there is the mushroom cards (I believe) which do take up less space.
You need to do an automation to achieve what you want with a button, no script necessary.
With regard to your Evohome I have no idea which takes precedent, i imagine the Evohome schedule would over the HA setup. I imagine whatever one is active takes control until the next schedule/ automation is fird off. Perhaps someone else can answer that.
Thanks @davidtja - can you provide an example of (YAML) code or screenshot for an automation? I am struggling as a new HA newbie here. Not about the press of a button, or motion detection, but how do I send a command to get it to set a specific temp? Action → device?
Its pretty basic stuff no need for yaml. Theres tons of great YouTube tutorials on automaions. Just make sure to watch newest ones.
Anyone else having the home assistant reported current temperatures change to the low precision ones since last night and/or new home assistant version? Before it would report current temperatures to a tenth of a degree i.e. 19,2, but now it’s following the same rounding as the display/controller does. When changing it will report the ungrounded value, but anywhere between 5 to 20 minutes later, the value is rounded. You can see it changing last night (for me). I did update HA OS last night, so it might have something to do with it?
Hi, I am having the same issue too.
A button with the following settings works for me.
show_name: true
show_icon: true
type: button
tap_action:
action: call-service
service: evohome.set_zone_override
target: {}
data:
entity_id: climate.woonkamer
setpoint: 18
duration: 0
entity: switch.automation_afwezig
icon: mdi:radiator
If the duration is 0 hours, then the change will be until the next setpoint.
If no period of time is provided then the change is permanent.
Thanks David.
It is working after using different characters in the password
red herring
HI, I’ve created a button which when I turn it on triggers a script to temporarily set the temperature of a number of zones which all works fine (I can see the new temp and end time in the evohome app).
When I turn the button off, it triggers a script to reset the temperature using evohome.clear_zone_override…it seems to remove the temporary override (i.e. the end time) but leaves the temperature the same…am I missing something?
*** I tried it a few times and realised that it can take up to 30 mins for the target temp of the zone to go back to the schedule. One of the zones is a radiator thermostat which takes about 10 mins, the other is a underfloor heating zone with a manifold which takes a lot longer ***