If you don’t see the entity, then either you haven’t restarted HA since the config file change, or the settings in the config file aren’t correct, or for some other reason HA can’t communicate with the Honeywell server. The log in Configuration / Logs should tell you why.
I just placed the WEB page link. I don’t see the entity listed so it sounds like I need the API needs to be listed in the Config file? How do I get that API I looked around the Honeywell page after logging in did not see a place get it? Just think I have this all wrong from the start, sorry for being so slow.
I’m just glad to be able to help; usually these threads get beyond my HA experience level too quickly!
First off, review the documentation at the link in my post #2, above. I know there isn’t much there, but that’s really all there is to it. You just need to add platform Honeywell to the climate: section of your configuration.yaml, then add your own username and password (the one that you use on the Honeywell web site) as shown. Of course, you want to run Check Configuration under Configuration / Server Controls to be sure there’s no syntax error.
The rest should be automatic once you’ve restarted HA. It knows how to reach out the the Honeywell servers using their API and the credentials you supplied in configuration.yaml.
If there’s any problem, it should show up in the log (Configuration / Logs). I’ve found it’s a good practice to always check this right after any restart.
If there’s no problem, you should be able to follow my second post to verify you’re receiving data.
This is good. The error message is pretty clear. HA sees your config entry for the Honeywell platform and tries to connet. The connection fails. The message even gives you three likely reasons why it failed. You’re lucky; not all HA log entries are this informative!
Taking the last one first, I doubt you’re being rate limited. The fact that you only got one message suggests HA didn’t try more than once, so it’s unlikely to have hit the limit. Of course, if you have the Honeywell app or web page open, and keep refreshing, that could impact HA’s ability to use the API, but I assume that’s not happening.
Most likely either the ID/Password is wrong, or the syntax defining them in the configuration.yaml is wrong.
If that works, triple-check the ID and password in the config file. Make sure any special characters are exactly correct (apostrophes and quotes come in various different styles.) Check upper/lower case. Make sure you use spaces and not tabs to indent those lines in config. If necessary, copy and paste so you’re positive you’re using the same values. Save the config file, validate it in HA, then restart.
When building the card in “Love Lace” I get error message “No card type configuration” . I’m using a manual card type and have the “simple-thermostat” file in the www directory?
The exact config from my ui-lovelace.yaml is posted above, along with a screenshot of how I display my zone(s). Would suggest using this as well as the custom-card’s documentation to configure exactly how you’d like it to appear
Hi CaptTom - I also have three Honeywell WIFI thermostats, but only one is showing up in HA for me. Did you have to modify anything within HA in order to have all 3 be available? Much appreciated!
There’s a known bug with the 8.x version of HA which causes exactly this symptom; only one Honeywell thermostat shows up in HA. I posted about it here, among other places: