Netatmo - no connection

m-a-r-z-e-l

Thanks for your help!

I had a look in the logs which were inconspicuous. But when I had a look in the console I found the following:

:8080/modules/netatmo/q.min.js:1 Uncaught TypeError: Cannot read property ‘dashboard_data’ of undefined
at Class.renderAll (:8080/modules/netatmo//netatmo.js:106)
at e (:8080/modules/netatmo/q.min.js:1)
at :8080/modules/netatmo/q.min.js:1
at o.d.promiseDispatch (:8080/modules/netatmo/q.min.js:1)
at :8080/modules/netatmo/q.min.js:1
at b (:8080/modules/netatmo/q.min.js:1)
at a (:8080/modules/netatmo/q.min.js:1)
at s (nunjucks.min.js:4)
at o (nunjucks.min.js:4)
at n (nunjucks.min.js:4)

I have no idea what’s going on…

sdetweil

@m-a-r-z-e-l said in Netatmo - no connection:

:8080/modules/netatmo/q.min.js:1 Uncaught TypeError: Cannot read property ‘dashboard_data’ of undefined

looks like the data either wasn’t received, or has changed format.

PetterT

Does anyone have any news on this? It seems as if the data structure in the Netatmo API has changed, making the current MM2-modules unusable? Or is it just problems on my end?

Thanks.

Fozi

@PetterT I had those connection issues, too. But recently I switched to a new fork, which works great and displays the information just as I always wanted. Here is the link

PetterT

@Fozi I am using that exact same fork - but without luck unfortunately. Are you using the module, and can you confirm that it works for you currently?

Fozi

@PetterT yes, it woks.

PetterT

@Fozi Sorry for being late to follow up. My error is as follows:
When I start up MM2, it shows that the module is loading. A spinning cycle shows in the middle of the screen. However, no graphics are shown - just the spinning cycle icon. I have double and triple checked the config.js file, and all seems correct there. No errors show up in the logs on the npm or in my web browser.

Any idea what could be wrong?

Tribun

@PetterT
If you only have a spinning circle in the middle, something is wrong with your login details. It may be that one of the values is incorrect: clientId, clientSecret or refreshToken. No error is displayed in the logs if the login did not work. I changed the registration data and was able to reproduce your mistake. If the data is correct, the module works fine for me.

edgeball

I’ve been having the same issue and it’s driving me n*ts. It works but only with 1 netatmo module. Only the base station. But whenever I try to add another one (moduleOrder: []) the spinning circle shows up.

sdetweil

@edgeball i would look to see if there is any error

either in the console where u start MM (npm start, or using pm2)
if pm2, then
pm2 logs --lines=100 will give u output

or in the developers window of the browser

ctrl-shift-i, select the console tab
and put a unique part of the module name in the filter field neta
in this case

the circle typically means busy, but then the code crashed and didn’t handle the error and can’t clear the busy