Skip to content
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

Open
fakethinkpad85 opened this issue Jan 27, 2023 · 9 comments
Open

Comments

@fakethinkpad85
Copy link

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'
`

@MuppetOwl
Copy link

MuppetOwl commented Jan 30, 2023

Can confirm same in my logs.
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.

@joggs
Copy link
Owner

joggs commented Jan 30, 2023 via email

@MuppetOwl
Copy link

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 have 8 in total, maybe a API limit issues?

@fakethinkpad85
Copy link
Author

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.

@MuppetOwl
Copy link

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.

@PerfectlyNormal
Copy link
Collaborator

Yeah, I think we should improve the error handling when talking to the API a bit. I've seen it intermittently, but not reliably.

@bions10
Copy link

bions10 commented Mar 8, 2023

I am still having this error. Any solutions how to solve it?

@joggs
Copy link
Owner

joggs commented Mar 9, 2023

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.

@bions10
Copy link

bions10 commented Mar 9, 2023

That worked. Thanks for an advice!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants