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

Authenticate problem #399

Open
thierry7100 opened this issue Jul 15, 2024 · 2 comments
Open

Authenticate problem #399

thierry7100 opened this issue Jul 15, 2024 · 2 comments

Comments

@thierry7100
Copy link

Hi,

I have installed the current version of your module to cope with the new Netatmo access policy. The old module was still working but was unable to run after a restart.
The new module was unable to load data.
I got the following message from the log file

[15.07.2024 10:11.46.661] [LOG] Netatmo: using refresh_token from config
[15.07.2024 10:11.46.661] [ERROR] Netatmo: refresh_token not set in config.

And after looking at the code, I think that the authenticate function in Helper.js is never called !
In the start function in netatmo.js there are the following lines
// best way is using initialize at start and if auth OK --> fetch data
this.sendSocketNotification('INIT', this.config)

But there are no INIT Notification entry in helper.js
switch (notification) {
case this.notifications.AUTH:
this.authenticate(payload)
break
case this.notifications.DATA:
this.loadData(payload)
break
}

There is a AUTH entry, but the corresponding line is commented out in netatmo.js ?

I am not skilled enough to correct this, so please help me.

I am using magic mirror on Ubuntu 22.04 but I don't think this is an issue. As said before, the old version was running quite well.

Best regards

@Lusbueb69
Copy link

I had to generate a new refresh token at Netatmo after the upgrade, after which the current version worked perfectly

@aop-ch
Copy link

aop-ch commented Aug 9, 2024

I had this issue two comming from the old version. I had to change the name refreshtoken to refresh_token in the config.js. May be this keyword did change.

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

3 participants