I’d recommend Tado, they have a monthly/yearly subscription now, but the product is great.
I saw this message on their site a couple weeks ago, but I filled in the form and still got the developer account info and it works with HA. So, seems they are still creating the needed keys/etc.
Did they email you the info after completing the form, or were you brought right to the interface? When I signed up the only option is to “Create new OAuth Client”, the rest of the interface for generating keys isn’t available.
Right in the interface. Filled in the form and on next page was the keys.
Like others said I saw the message a week or two ago and still was able to get key and make thermostats and hello doorbell work. Doorbell was a little finnicky at first but after some troubleshooting its solid now.
Yeah. I was able to too, the docs just don’t match the interface 100% so when things weren’t matching (and having seen the message on the page), I assumed some feature I needed was going to be missing.
The new interface just has a button that says “Create new OAuth Client”. So in the docs, steps 4 & 5 don’t exist now. The rest of it follows though.
(I’m in the US.)
Does anyone use Radio Thermostat (CT50/CT80) as an alternative to Nest? What are the alternatives with local AIP access? Protocol (Wi-Fi, Zigbee, Z-Wave, etc.) does not matter to me.
It seems to me that anything that looks very modern and sleek-looking such as Nest or Ecobee would require Internet access, so it makes sense that I should not care for the modern looks when choosing a thermostat; however, that can be worked around with an in-wall tablet with a modern thermostat interface that connects to Home Assistant.
I use Radio Thermostat CT50’s in my house. No cloud access is required for HA integration and there is native support. All I do is use a DHCP reservation for each thermostat so I don’t have to worry about IP changes impacting discovery and use the IP’s in the HA climate module. Radio Thermostats have a full REST API so they will continue to work long past when/if support is discontinued. The CT50 has 2 “USNAP” modules that can be populated with radios. They normally come with an included WiFi module and you can add a second Z-Wave or Zigbee module. I just use mine with the included WiFi module.
Just a warning though, they are some of the ugliest thermostats you can find. When I purchased them, looks were at the bottom of my list. I bought for price and the local API.
1 Like
Looks are at the bottom of my list when it comes to thermostats, which is sad IMO. But yeah, Radio Thermostat is a good way to go for local control with Home Assistant. At least the thermostat supports multiple stages for heading and cooling, which is a good thing if I have a unit that supports it, including humidity.
Also a question about the forum: is it just me or has the forum administrator removed my photo of me from my profile? I used to have it there besides my name in my post and in the top-right hand corner of the web page. Looks like I’ll have to add it back manually.
It was there yesterday.
Oh, I know why. I was using Gravatar that’s based in an email address. I changed my email address to be unique for every site that I register with.
I have a CT80 with zwave control. Works well, but auto-creates four climate entities, heat_normal heat_econ, cool_normal, and cool_econ. Only difference is the default set-points between econ and normal. All other attributes and state values are the same across them all. So, I use the custom:Dual-Thermostat lovelace card to switch between heat_normal and cool_normal climate entities.
I also created two custom sensors, one for Operating Mode and another for Operating State. These are useful for automations, etc. Here’s the code:
#~~~~~~~~~~~~~~~~~~~~~~~~~
# custom sensor that tracks the mode set for the HVAC.
# This reports what its set to, not what its doing.
# All of the four CT80 "climate" entities show the same properties
# Use "heating" because its now wintertime, no other reason.
# While the fan could be forced on during non-off modes,
# only report "fan" as mode when system is otherwise off and fan is on.
#
- platform: template
sensors:
hallway_hvac_mode:
friendly_name: 'Hallway HVAC Mode'
value_template: >-
{% if is_state('climate.hallway_thermostat_heating_normal', 'heat') %}
Heat
{% elif is_state('climate.hallway_thermostat_heating_normal', 'cool') %}
Cool
{% elif is_state('climate.hallway_thermostat_heating_normal', 'auto') %}
Auto
{% elif is_state('climate.hallway_thermostat_heating_normal', 'off') %}
{% if is_state_attr('climate.hallway_thermostat_heating_normal', 'fan_state', 'Running') %}
Fan
{% elif is_state_attr('climate.hallway_thermostat_heating_normal', 'fan_state', 'Idle') %}
Off
{% else %}
Off-unknown
{% endif %}
{% else %}
On-unknown
{% endif %}
#~~~~~~~~~~~~~~~~~~~~~~~~~~
# custom sensor that tracks the operating state of the HVAC.
# This reports what its doing, as opposed to what mode is set.
# Report Fan-only if fan is running and the system is neither
# actively heating or cooling, otherwise its Off.
- platform: template
sensors:
hallway_hvac_state:
friendly_name: 'Hallway HVAC State'
value_template: >-
{% if is_state_attr('climate.hallway_thermostat_heating_normal', 'operating_state', 'Heating') %}
Heating
{% elif is_state_attr('climate.hallway_thermostat_heating_normal', 'operating_state', 'Cooling') %}
Cooling
{% elif is_state_attr('climate.hallway_thermostat_heating_normal', 'fan_state', 'Running') %}
Fan
{% elif is_state('climate.hallway_thermostat_heating_normal', 'off') %}
Off
{% elif is_state_attr('climate.hallway_thermostat_heating_normal', 'fan_state', 'Idle') %}
Idle
{% else %}
Unknown
{% endif %}
Oh, also I refresh the status of the thermostat ever five minutes with an automation. Polling only updates the set-point, not all the attributes, or the state.
#~~~~~~~~~~~~~~~~~
# Refresh thermostat information
# CT 80 is not good at self updating when its state changes
# This will refresh every five minutes
# Note that it takes about 3 seconds for the thermostat
# to update once requested.
#
- id: 'refresh_thermostat'
alias: 'Refresh Thermostat Status'
initial_state: true
trigger:
platform: time_pattern
minutes: '/5' # e.g., minutes divisible by five
seconds: '00' # seconds needed so it doesn't match every second of minutes
action:
service: zwave.refresh_node
data:
node_id: 3
1 Like
I have just installed a Nest Protect and was dismayed to then see this post.
Anyway I’ve gone through the Developer application process with Nest, and despite also getting the Suspension Message at the top of the page, I was able to proceed with acquiring a Client ID and Secret, and have just completed configuring it in HA.
Happy days…so far!
1 Like
Where do you see the Client ID and Secret? I’ve looked everywhere. I am wondering if I need to re-sign up new? Only option I have is to “create new oauth”, “update my profile”, “go to docs”, and “feedback.”
I really want to get my Nest products integrated.
Like, if someone maybe has the url for the key generating service?
Check my post here: Nest locks users out of their own data
You want to use the “Create new OAuth” button, then follow the docs.
1 Like
@levickij. Very interested in your Wiser integration. I am looking for a control system and was wondering if this system could do the job. Like you I have 8 zones to control and was put-off by the Drayton at a show as they said it can only control three (two heating + plus hotwater). Not sure how we could communicate directly if this is not appropriate to the forum as only just joined but would love to know more and perhaps share you NodeRed data.
When you say zones, the controller has channels/relays to switch open/close a motorized “zone” valve, plus a hot water channel. So depending on which kit you go for, kit 1 is for a combi boiler with single channel, kit 2 has 1 heating channel and 1 hot water channel, or kit 2 has 2 heating channels and a hot water channel. The hub offers multi-zone which is wireless zigbee of individual radiators on top of this, so in addition to the hard wired motorized valve for the zone (say your house is separately zoned circuits for upstairs and downstairs), you then individually control each room radiator to a setpoint/schedule, or if you have multiple radiators, these can be grouped into a room. When the wireless TRV calls for heat the appropriate channel shall drive the zone valve open. As my home only has a single zone heating zone circuit, all radiators shall be on, now with Wiser I can switch the ground floor rooms off and only heat the bedrooms to a setback setpoint during the cold nights.
Look on the Drayton website, it has all the info on configuration there.
Ok, understand thanks. I’m looking for a system to work with Home Assistant that can operate 6 or more zone valves. So putting aside the Drayton control box are you able to interface/connect each Wiser thermostat to Home Assistant so as to allow HA to do the control logic (via the gateway; which I know is in the control box)? It would seem so from the screen picture included in your original post above. have plenty of output control relays (Sonoff/Tasmota) that can be used to control the zone valves. Would be very grateful if you could make a copy of your NodeRed flows available somehow; Github perhaps?
Yes the Heat Hub is a gateway to all the zones/TRV’s, these are all accessible to control individually through the API, unfortunately I can’t help much at the moment as the Pi is down, I now have a corrupted SD card, used the genuine Pi power supply, and quality branded Samsung Evo SD card recommended on the web, given this has lasted only a few months I am now looking at bringing this back up on a new and more stable platform.
I’m new to home assistant and was shocked to see that integration with nest is no longer available. I’m currently using an ISY994i and have full integration with the use of the Polyglot 2.0 and this integration https://github.com/Einstein42/udi-nest-poly. There is no need for a developer account and it work great. Hopefully someone much smarter than me can determine what method is available and port over to work with Home Assistant.