Honeywell Lyric Thermostat

Feature Requests
610

should be:
config/custom_components/lyric/init.py
config/custom_components/lyric/climate.py

611

Thank you druknmonkey ,
So I presume that the post of Bram_kragten on Jan ’17 is not the correct place to start.
Can you tell me where in this topic I should start reading to set this up working?

612

Yes, check this one

613

So I had to change my thermostat from a honeywell TCC ( which integrated well) to a lyric-based T6-wifi pro. I have been trying to add this to my custom_components and I get Configuration invalid CHECK CONFIG

Integration not found: lyric
I am on ver 0.94.2
I have custom_components/lyric folder structure in my config folder.
I downloaded the files located here and placed them in custom_components/lyric/ and have restarted homeassistant multiple times and cannot get it to find/load the lyric integration. I am running hassio on a pi3.
I find this line in the log file,
ERROR (MainThread) [homeassistant.setup] Setup failed for lyric: Integration not found.
For the life of me, I cannot get it to see the new integration. I feel as though there is something missing from my setup, but I am not finding it.
In my configuration.yaml I have
http:
base_url: http://100.75.1.22:8123/
and
lyric:
client_id: redacted
client_secret: redacted

614

At this time I am abandoning this approach to integrating my honeywell T6 wifi pro. I have successfully implemented the thermostat using the HomeKit controller support. The only issue I had with this integration is you must have the pairing code off of the box the thermostat comes in and I am 900 miles away. Fortunately, I was able to contact my installer who found the code for me.

615

Has anyone had any success getting this to work with the new HACS (home assistant community store) component? I had it all working great for last several months while running hassio 92.? and custom_components. Then i had to do a fresh hassio install due to another issue and upgraded to 0.94.4 and installed the HACS component and installed lyric from there. Every thing went really smooth it installed and rebooted and got the authenticate alert. But this is where the problem started, when i click “configure” then “Request Authorization” the login page for Honeywell pops up and i login then it finds my thermostat, i select it then click “connect” and i get an error stating “500 Internal Server Error” . I have tried several times with the same result, i have updated my ip on honeywells site and even added this to my config.

http:
  base_url: http://192.168.1.111:8123

All with no joy.
Any ideas would be greatly appreciated!!!

Update:
I just noticed this in the hassio log , not sure what it means though.

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 418, in start
    resp = await task
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_app.py", line 458, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.7/site-packages/aiohttp/web_middlewares.py", line 119, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/real_ip.py", line 33, in real_ip_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 67, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 216, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 115, in handle
    result = await result
  File "/usr/local/lib/python3.7/asyncio/coroutines.py", line 120, in coro
    res = func(*args, **kw)
  File "/config/custom_components/lyric/__init__.py", line 199, in get
    data = request.GET
AttributeError: 'Request' object has no attribute 'GET'

Update:
I got it working! Not sure what exactly fixed it but i had a backup of my previous “lyric” folder from custom_updater so just for giggles i swapped the entire lyric folder out with my old one from before i installed HACS and whala it finished the auth process and is working great. So maybe the "Lyric " folder that is being installed with the plugin from HACS has a problem or maybe it was something i did but i did swap them back and it would not work so i am not sure what the difference is but it works fine with my old “lyric” folder.

617

I been getting the same problem. I like the ‘stat’ and i really think it should work with HASSIO

618

Update: I never was able to get the lyric integration used with the old Honeywell 'stat but the Homekit controller support has been working fine EXCEPT there seems to be no support to show the fan status. There is support for the current operating mode, (Cool, Heat, Idle) but nothing to indicate the current status of fan-only operations.

619

Don’t I need a Mac for Homekit?

620

I don’t think you need the Apple Homekit, I think the plugin emulates it, but I know when I tired this way I didn’t have luck.

Since it’s summer probably not a lot of people monitoring this thread right now. I know I’ve had my Lyric off since early May so have needed to us HA with it right now as I don’t use it for AC.

621

latest updates to the Climate component(s) breaks the current version of Lyric, FYI. Wait to update if you rely on this custom component.

622

Are you saying 0.96.1 breaks it?

623

Are you looking into it? Or can you post the error log?

624

Just tried upgrading saw this in the error log

> 2019-07-19 18:53:24 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform lyric.climate: Platform not found (cannot import name 'STATE_AUTO' from 'homeassistant.components.climate.const' (/usr/src/homeassistant/homeassistant/components/climate/const.py)).

625

That’s correct.

‘Climate 1.0’ is a major effort to to redesign the climate component (all climate platforms are based on this ‘parent’ component). Several things have changed including the names of various constants. STATE_AUTO was a constant in the previous version of the climate component but no longer in the new one.

List of climate component constants.

This Honeywell Lyric component will require revision to have it meet the new standards set by the ‘Climate 1.0’ initiative.

626

Darn, just finished the 0.96.1 update and saw this, guess I’ll be reverting to a snapshot. Hopefully @teunehv can make some changes to support the new climate structure.

627

Since it seems to me like a big change I’m not sure if I can fix it since I’m not that experienced in programming.

The full pull request of the change in. 96 is here:
https://github.com/home-assistant/home-assistant/pull/23899

I hope to find some time during the weekend to look into it. But all help is appreciated.

Edit: based on a first analyse I think it’s fixable by replacing all removed contants by the new ones. Will check this weekend when I’m near my computer.

628

I can’t say I have a complete understanding of all the changes but I’ll share what I do know:

There is now a clear separation between the operation mode (the task it will perform: auto, heat, cool, off, etc) and the operating state (the task it is actively performing: heating, cooling, idle). The component’s state continues to represent the operation mode but now it has a new attribute to represent its operating state. The History Chart used to graph the climate component’s state but now it graphs the new attribute. That means the shaded area on the graph will correctly indicate when the HVAC system is actually heating or cooling.

To support this new ability (distinguishing between operation mode and operating state), several constants have been removed and replaced by new ones.

The ability to hold a temperature has been incorporated into a broader concept known as ‘presets’. Presets can be as simple as ‘hold’ (meaning to ignore the schedule and hold this temperature indefinitely) to more complex situations like ‘away’, ‘vacation’, etc. There is now a new service call set_preset_mode which replaces previous ones like set _away_mode.

629

Too bad, it’s more then just replacing the constants. Got locally another message now about not implemented hvac_mode. Hope to find time for further analyse, but as mentioned I’m not a programmer so it’s all just trial and error.

Update July 22:
got rid of a lot of different errors with help from other climate related forum posts. But it’s not working yet. Will continue tomorrow with the hope it will be fixed then.

630

Good news, I’ve got the custom component up-and-running again. See the repo for the updated climate.py

Two notes:

  • I saw already an error in one of my automations. The operation mode is replaced by hvac mode. So perhaps updates on automations is needed int this case.
  • I didn’t had time to test the changes. I didn’t change functionality as far as I’m aware, but I can’t oversee all consequences of the update. If you experience problems please post them here so we are al aware.
1 Like