Read the statement by Michael Teeuw here.
Netatmo - no connection
-
@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?
-
@PetterT yes, it woks.
-
@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?
-
@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. -
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.
-
@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 outputor 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 casethe circle typically means busy, but then the code crashed and didn’t handle the error and can’t clear the busy
-
@sdetweil
thanks for the reply. The problem was the netatmo. I reset it and now it works fine. Weird. But I didn’t have to change anything else. -
I am using this one, and it is working nicely.