-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in log, 'NoneType' object has no attribute 'accessToken' #23
Comments
Can confirm same in my logs. I get this error 3-10 times every hour. Started 1-2 weeks ago. Thermostats are working but some times repond slow or have status unknown for some minutes. |
Hi guys.
I cannot replicate the problem unfortunately.
Have you tried to reconfigure or remove/add the integration?
I had to do that early january, where my accesstoken stopped working
…On Mon, Jan 30, 2023 at 5:13 PM Dennis ***@***.***> wrote:
Can also confirm same issue.
Error fetching Ebeco data: 'NoneType' object has no attribute 'accessToken'
I get this error 3-10 times every hour. Started 1-2 weeks ago. Thermostats
are working but some times repond slow or have status unknown for some
minutes.
—
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACLJXNMPZV64HQ3QN5VVQTWU7SA3ANCNFSM6AAAAAAUI6OWLU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
/Jörgen Bergström
|
Hi, Did try to remove all my Thermostats from the Ebeco integration, restart and add them back. Still get the samme error in the logs and they go to unavailable for while. |
I havent tried to reconfigure yet, but its a fairly new HA installation and never had any issues before, like @MuppetOwl said, it started a few weeks ago for me as well. i will try and reconfigure the integration this weekend hopefully and see. |
Last time I did see the error appear I tried to use the Ebeco Connect app and it was not able to show my thermostats at all or very slow . So think this is a Ebeco server issue, maybe only for some locations. Will guess they have different servers for different locations. Have not seen the error at all the last 10 hours. |
Yeah, I think we should improve the error handling when talking to the API a bit. I've seen it intermittently, but not reliably. |
I am still having this error. Any solutions how to solve it? |
It has been working very well for me since Ebeco solved the problems they had with the overload attacks, so my log has been clean of ebeco errors since then. The only thing I did was removing and reinstalling the addon. When I spoke to the Ebeco developers during the troubling period, they said they had't changed anything in the api. |
That worked. Thanks for an advice! |
I have started getting this error in the log,
`
Logger: custom_components.ebeco
Source: helpers/update_coordinator.py:168
Integration: Ebeco (documentation, issues)
First occurred: 18:33:12 (1 occurrences)
Last logged: 18:33:12
Error fetching Ebeco data: 'NoneType' object has no attribute 'accessToken'
`
The text was updated successfully, but these errors were encountered: