Hello,
I am having trouble getting the MMM-Netatmo module to work. It is permanently stuck on the "Laden..." (Loading...) screen.
I have tried every possible solution for many hours, but the problem persists. The developer console shows the final error: DATA FAILED, refreshing token.
This is what I have already done:
- Confirmed my
config.js is 100% valid using npm run config:check.
- Updated the module to the latest version by deleting the folder and re-cloning it from GitHub (
git pull also confirmed it's up-to-date).
- I am using the correct new configuration structure with the separate
auth: block.
- I have created a completely new app in the Netatmo Dev Portal multiple times.
- I have generated new tokens multiple times, ensuring the
read_station scope is selected.
- I have tried all variations of the
refreshToken (the full token, the part before the |, and the part after the |). The error in the console remains the same.
- The
moduleOrder is set correctly with the exact names of my modules from the Netatmo app.
This seems to be a deeper issue with the token validation process. The module correctly identifies that the token needs to be refreshed, but the refresh process itself seems to fail silently on the server-side.
`My Configuration:
(I have replaced my secret keys with placeholders)
{
module: 'netatmo',
position: 'top_center',
header: 'Netatmo',
config: {
refreshToken: 'PART_AFTER_THE_PIPE',
moduleOrder: ["Innenstation WZ", "Außenstation", "Innenstation AZ", "Regenmesser", "Windmesser"]
},
auth: {
clientId: 'MY_CLIENT_ID',
clientSecret: 'MY_CLIENT_SECRET'
}
}`
Could you please look into this? It seems I have exhausted all user-side troubleshooting steps. Thank you!
Hello,
I am having trouble getting the MMM-Netatmo module to work. It is permanently stuck on the "Laden..." (Loading...) screen.
I have tried every possible solution for many hours, but the problem persists. The developer console shows the final error:
DATA FAILED, refreshing token.This is what I have already done:
config.jsis 100% valid usingnpm run config:check.git pullalso confirmed it's up-to-date).auth:block.read_stationscope is selected.refreshToken(the full token, the part before the|, and the part after the|). The error in the console remains the same.moduleOrderis set correctly with the exact names of my modules from the Netatmo app.This seems to be a deeper issue with the token validation process. The module correctly identifies that the token needs to be refreshed, but the refresh process itself seems to fail silently on the server-side.
`My Configuration:
(I have replaced my secret keys with placeholders)