search

scambo00 / NodeRed-Honeywell-Lyric-API

NodeRed Honeywell Lyric API
6 stars 3 forks source link

Authorization denied #5

Open drsurfer opened 2 years ago

drsurfer commented 2 years ago

Hi, I have configured my Lyric Thermostat and I wrote a flow to log temperatures every 10 minutes on a google sheet.

It has worked like a charm for about a week, then I started to got authorization denied errors like this: image

I repeat the authorization on Honeywell/Resideo website and it start to work again, until the next failure.

It may happen minutes later, or hours... I don't see any pattern in this.

Do you have any suggestion to overcome this problem?

FrankX0 commented 2 years ago

I encounter the same issue. IMO this is caused by a (temporarily) failing network connection, of which the current implementation cannot automatically recover from. I will try to see if I can come up with a solution, although this could take some time.

FrankX0 commented 2 years ago

Seems to be this issue: https://github.com/home-assistant/core/pull/62100

FrankX0 commented 1 year ago

@drsurfer please give the latest flow a try (if still interested). I have seen this version recover from error situations.

drsurfer commented 1 year ago

@drsurfer please give the latest flow a try (if still interested). I have seen this version recover from error situations.

Sorry for the delay in responding - we've had a huge loss in the family so the least of my problems is playing with the thermostat :-( I'll check as soon as we get back to some sort of normality. Thanks for working on my problem, I really appreciate it.

FrankX0 commented 1 year ago

No worries: there are more important things in life than thermostats! Take care, Frank.

drsurfer commented 4 months ago

Hi Frank. I know it's been over a year and maybe you're still waiting for a response, so here I am. The frequency of "Authorization denied" messages has been greatly lowered by the changed flow, but it still happens sometimes. It's only happened two or three times since then, and once three days ago, and it reminded me that I had something to deal with... Like last time, I don't know what to attribute this behavior to. If I can suggest an improvement, it would probably be helpful to report this type of error somehow, so you can handle it manually. Another improvement could be to automatically fill the "Redirect URI" and "App Name" fields as well, and not just those relating to the "Key" and mispelled "Secert" Thank you for your patience