Also you need to copy the climote folder in custom_components, then restart home assistant and then make yml modifications to include the integration.
HA has changed and it mandates that yml config is correct before restarting.
Thanks Adrian,
The zip you just shared has the identical files you shared on Aug 22 - I’ve got them in my system. Got my Climote app password updated also.
So steps I followed now:
-
Dropped the files to the server in /config/custom_components/climote/ with no update to the configuration.yaml
-
Confirmed valid configuration (Dev Tools > Yaml)
-
Restarted
-
Updated configuration.yaml as per your latest comment including new password and saved it
-
Tried confirming valid configuration (Dev Tools > Yaml), but only got a spinning circle with no result, as well as not working Restart button
-
Rebooted device by unplugging the power
-
Configuration is now valid
Wondering if there is a lead time for entities to appear for selection?
Thanks, Alex
Hello,
I do not use those identities. I used those custom buttons and some rules that is calling the services see example how I turn on and off water heating using those custom booleans and timers that I have in my previous code. That served my purpose…
I / we should really put together a HACS project to deal with this integration, I should be able to start it but I never got the time…
HTH!
alias: Boost_water_on
description: ""
trigger:
- platform: state
entity_id: input_boolean.boost_water
to: "on"
condition: []
action:
- service: timer.start
data: {}
target:
entity_id: timer.heating_water
- service: climate.set_hvac_mode
data:
hvac_mode: heat
entity_id: climate.water
mode: single
alias: Boost_water_off
description: ""
trigger:
- platform: state
entity_id: input_boolean.boost_water
to: "off"
condition: []
action:
- service: timer.finish
data: {}
entity_id: timer.heating_water
- service: climate.set_hvac_mode
data:
hvac_mode: "off"
entity_id: climate.water
mode: single
alias: Boost_water_done
description: ""
trigger:
- platform: state
entity_id: timer.heating_water
to: idle
for: "00:00:02"
condition: []
action:
- service: automation.turn_off
data: {}
entity_id: automation.boost_water_on
- service: automation.turn_off
data: {}
entity_id: automation.boost_water_off
- service: input_boolean.turn_off
data: {}
entity_id: input_boolean.boost_water
- service: automation.turn_on
data: {}
entity_id: automation.boost_water_on
- service: automation.turn_on
data: {}
entity_id: automation.boost_water_off
mode: single
HI Guys,
I need your help setting up Climote within HA.
I used Andy73 climote.zip, added configuration to configuraiton.yaml and i’m getting following error in HA logs.
What have i missed or did wrong? THX!
I have tweaked existing versions of this and got it working again.
Repo link below for anyone looking for a working version.
Hi Brianbola,
First thank you for your effort on this.
I have followed your instructions.
-
git into custome_componenets (which creates folder home_assisntat_climote with your files inside)
-
added conifig to configuration.yaml
-
tried to restart home assistant but it complains about this…
-
i removed config from configuration.yaml and i was able to restart HA.
-
after reboot i added config back to configuration.yaml and tried to restartbut i got this…
-
again removed config from configuration.yaml and change path from custom_components\home-assistant-climote\ “all you files” to custom_components\home-assistant-climote\climate\ “all your files” and rebooted HA
-
again i added configuration back to configuration.yaml and tried to restart HA but i got this…
And now i don’t know what to do next… Please any advice on how to get it working.
@Storo Oh My bad It was just a naming problem meant to be climate.py not climote.py.
if you do a git pull with latest change it should work for you.
Just a FYI Because It is using requests and web scraping its probably best just to use this component for automations the thermostat widget is a bit buggy with it.
@brianbola Thx so much! i tried it now and finally i got sensors with readings from thermostats.
Awesome job!
@brianbola Can you please let me know the following…
- How to change boost time from 1h to 30 min?
- Is there a way like with custom cards to add effect (red color) on “fire” icon when heating is turned on?
Also if you will continue to develop this project maybe to add time counter how long boost will last like on climote app would be nice.
Hi, is anyone using or has anyone integrad Climote Immersion switch (Climote smart immersion controller) in HA? I’ve traced some API calls and am able to monitor the hot water tank through REST but a more robust integration will be needed.
Hi, You should contact climote support Get Your Questions Answered and Issues Resolved
They are very helpful I had some long discussions with them on the Climote Heating Controller where there is no yet an API but maybe they have one for Immersion controller.
Good luck
I’ve been working on an updated version of this over the last few days. It still has a lot of changes needed under the hood (TODOs include a datacoordinator, cleanup of the climate entity and climote service, improved countdown timer…) but its starting to come together.
The updates are mostly UI related like:
- Using a config flow
- Switching i/o to be outside of the event loop
- HACS install
- Configurable per zone boost duration
- Countdown sensor
Still very much WIP, with its logging exposing secrets and its my first HA project so some parts could have fundamental compatibility issues.
If you add it to the custom repositories in HACS, it will then come up:
Restart HA, go to add integration, find climote and add in details.
The numbers are how long you want each zone to boost, the last 4 digits of the climote are shown as the default entity names.
Congrats that looks promising … I wish to have time to contribute myself… for now what I have it does it job but that HACS project is the way to go.
When you have a more stable version let me know and I can try it out.
Hey,
This has been working great, doing exactly as it’s supposed to. This morning however the heating isn’t firing and on investigation I find this error at the bottom on the web UI for Climote.
Contacted Climote and they’ve reset the credit count but they advised that limit is 60 per week. Is there a way to overcome this?
Got my account also frozen. Had to call them up to get it reset. The guy on the phone said about 500 API calls are allowed per month (one API call = 1 SMS). Even their own app uses two calls every time to set boost (1 to get latest status when the app opens and second one to send the boost command).
Also they replied that there is no way this number can be increased in the current implementation.
I will be switching to genius hub (formerly heat genius) who have their own web-based API. And I had successfully used in my last house.
Or even better, get my own implementation using zigbee based radiator valves and home assistant. I will be able to control individual radiators and no more reliance on third-party! Just waiting for permission from the missus.
if anyone can find a direct replacement of climote to a zignee or wifi device with local API I will be very happy. SMS integration and subscription not nice…
Hi Andy. I find RFLightwave is great. The boiler switch would be a drop in replacement. Need a hub too though.
I like the climote for a no Internet location. Though to get around its limitations, I’m now looking to get hold of an IOT SIM card and use MQTT (low data use) to control and monitor additional things like lights and humidity remotely.
I too had my account frozen after many months of it working ok. If anything, i’ve been doing less requests lately!
I can still control the hub remotely using text commands climote SMS | Climote
integration stopped working (I still use the local one not the github version) and it seems that they dumped the password in the authentiction. I have sent an email to their support to ask if is a bug or something to stay.
In the code I have changed
vol.Required(CONF_PASSWORD): cv.string
to
vol.Optional(CONF_PASSWORD): cv.string
to allow removing the password from the config.
I am still looking for a direct replacement for something that is not subscription based 