Thanks for this, I will look into the RF Integration as it could contain some of the parameters that I have asked @andremain over on the Smartthings side before he moved to Home Assistant, such as the % Demand setting that a zone is at e.g. Lounge - 80%.
With respect to PR I’m assuming that you mean Pull Request ? But coming for a Demand Management background you could also mean Product Request. Can you please clarify what you mean !
Having problems with making automations with the evohome integration.
For some reason I do not find and entities when creating an automation.
But the climate entities are present.
Someone who can point me in the right direction?
While i did make the latest Evohome integration for Smartthings, i am really not a developer, I got a lot of help from Nayely. I hope you manage to achieve what you are looking for.
Hi I set up a simple How water on for 30 mins schedule as a boost with a hot water off as the final part of the automation. Unfortunately the off sets as permanent rather than reverting to schedule. Can someone advise what command sets it back to the schedule (as set in the Evohome app)?
Thanks
I resolved my issue. Stupidly I had another automation that I used for testing turning it off. Check on the entity to see what automation are linked to it. Here’s what works for me.
alias: "Water heater on for 20 minutes "
description: ""
trigger: []
condition: []
action:
- service: water_heater.turn_on
entity_id: water_heater.dhw_controller
alias: Water Heater On
- delay:
hours: 0
minutes: 20
seconds: 0
milliseconds: 0
- service: water_heater.turn_off
entity_id: water_heater.dhw_controller
enabled: true
- service: water_heater.set_operation_mode
data:
operation_mode: auto
target:
entity_id: water_heater.dhw_controller
enabled: true
mode: single
For people still wanting to do this:
In manifest.yaml you have to add:
"version": "1.0.0"
(And don’t forget to add a “comma” since it’s a list you’re adding it to)
Without the version string, the custom component won’t load and you will get strange errors.
I’m not sure if this is the right place, but is anyone else having issues with this integration and Honeywell locking them out of the account? I have received this from Honeywell
"
The account was locked due to multiple requests to the server since 5th of May, but we have successfully unlocked the account.
Please remove any automation system you might have installed, and please be aware that if you will be creating the same number of high requests to the server, the account will be locked again automatically
"
I got absolutely no warning at all it all just locked up. It took a fair amount of bashing their customer support to get that far. If nobody else has issues I might re enable on a tertiary account with an hour poll time to see if that helps.
It does seem stupid to have such a system and allow integrations and then get annoyed when people use it. It would also be better for them to have an mqtt type pub/sub thing rather than an API for these things.