core: Honeywell Lyrics becomes unavailable every 4 to 8 hours
The problem
OK so here goes… first, I’m not a programmer and HA is a bit overwhelming. My goal is to turn my HVAC off when someone leaves a door open for too long. My alarm system is Alarm.com. In the configuration file, I’ve setup the Honeywell Lyrics integration per the instructions. I’ve setup HA to read notification emails from Alarm.com and I’ve setup an automation to turn the HVAC off or on based on the subject of the email. I believe this all works fine until Lyrics becomes unavailable. When Lyrics does become unavailable, I am still able to see both Honeywell T9 thermostats on my app. Reauthorization is simple without any issues… its just a pain.
What is version of Home Assistant Core has the issue?
core-2021.5.5
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Honeywell Lyrics
Link to integration documentation on our website
No response
Example YAML snippet
# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:
# Text to speech
tts:
- platform: google_translate
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
lyric:
client_id: xxxxxxxxxxxxxxxxxxxx
client_secret: yyyyyyyyyyyyyyy
sensor:
- platform: imap_email_content
server: imap.gmail.com
name: doors_status
port: 993
username: zzzzzzzzzzz@gmail.com
password: xxxxxxxxxxxxx
senders:
- notifications@alarm.com
value_template: >-
{% if 'Door was left open' in subject %}
doors_are_open
{% elif 'issued a Sensor-Left-Open restoral' in subject %}
doors_are_closed
{% endif %}
Anything in the logs that might be useful for us?
2021-06-01 05:59:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.doors_status is taking over 10 seconds
2021-06-01 05:59:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.doors_status is taking over 10 seconds
2021-06-01 06:00:07 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.doors_status is taking over 10 seconds
2021-06-01 06:00:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.doors_status is taking over 10 seconds
2021-06-01 06:00:58 ERROR (SyncWorker_4) [homeassistant.components.imap_email_content.sensor] Failed to reconnect
2021-06-01 06:01:37 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.doors_status is taking over 10 seconds
2021-06-01 06:01:59 ERROR (MainThread) [homeassistant.components.lyric] Authentication failed while fetching lyric_coordinator data: {'request': {'method': 'GET', 'url': 'https://api.honeywell.com/v2/locations?apikey=xxxxxxxxxxxxxxxxxxx', 'headers': {'Authorization': 'Bearer xxxxxxxxxxxxxxxxxxxx', 'Content-Type': 'application/json'}}, 'response': {'code': 'Unauthorized', 'message': 'Authorization has been denied for this request '}, 'status': 401}
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 4
- Comments: 98 (9 by maintainers)
Been happening constantly recently, not sure what is happening and havent had time to investigate. In the latest beta we reduced the calls to the api but it hasnt seemed to help (at least for myself)
`alias: Algemeen) Honeywell Unavailable description: ‘’ trigger:
This automation helps to fix it not ideal but a fix for now
Yes. There Is a reset option under settings. Don’t worry about wifi or other configs they Will remain as they are.
Il mer 3 nov 2021, 13:00 Oulewappeur @.***> ha scritto:
Node Red config for anyone interested:
Watchdog has two triggers: a state change to
unavailable, and a poller that checks forunavailablejust to be sure (this can be optional, I haven’t tested the state change to ensure it works as expected so the poller acts as a fallback).It then sets the entity (which fixes the integration), then checks to see that the entity is no longer
unavailable. If it’s still unavailable (there have been reports from @LouisMT that it sometimes takes more than one go), it waits 1min then tries again.Also note that I have two thermostats, so you can remove one if you only have one. My state node uses regex to get all entities that start with
climate..@sven41 Thanks, it works great.
I observed in my logbook that the automation sometimes starts 2 or 3 times instead of just once. Perhaps Honeywell is then unavailable for 10-15 minutes? Anyone noticed this?
Correct me if I wrong but as I understand it his automation should run EVERY time the state changes not just once. However, if you had to reboot HA and the initial state after boot for the Lyric was unavailable the automation would miss it because there was no state change since boot, so you would really need a second automation for boot specifically.
Edit: In your code your trigger and condition do the same thing.
@justinmbrock I agree that would generally be a better option, but your automation only updates the entity once (when it becomes unavailable), while @sven41’s automation will keep doing this every 5 minutes as long as it stays unavailable. As it seems that the API is unstable at some times, I think this might be just what makes it work. 😄
I’ve combined both of your automations, it’ll fire as soon as the integration becomes unavailable (so in a best case scenario you won’t even notice that it has become unavailable) and keep retrying every 5 minutes. Hopefully this works for me too, I just started it! 😄
Edit: the automation was triggered 3 times before the integration recovered.
Is it not recommended to use something like the state change as a trigger? Something like this:
Same here. In just the last 24 hours I have had to re-auth 3 times. Starting to drive me nuts. The honeywell thermostats are great other than this issue. I agree with what some other folks have said about a possible change to the API. I’m running the latest version with the fix like others (2021.10.6). Any solution in site on this one?