MMM-Tado not working.

[sdetweil]

@Wrangler ok, got it…

MMM-Tado has a bug really… it USES stuff but doesn’t document them

const TadoClient = require(“tado-client”);
const logger = require(“mocha-logger”);

but there is no package.json, and he loads a previous copy of node_modules in his folder which is now out of synch

so, you need to do these updates manually

cd MMM-Tado
rm -rf node_modules
rm package-lock.json
npm install tado-client --save
npm install mocha-logger --save

then you can restart MM and it should work…

my script looks for package.json, and there isn’t one…

[Wrangler]

@sdetweil said in MMM-Tado not working.:

No luck ```

pi@MagicMirror:~/MagicMirror/modules/MMM-Tado $ npm install tado-client --save
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/tado-client - Not found
npm ERR! 404 
npm ERR! 404  'tado-client@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2020-05-30T14_54_13_631Z-debug.log
pi@MagicMirror:~/MagicMirror/modules/MMM-Tado $

pi@MagicMirror:~/MagicMirror/modules/MMM-Tado $ npm install mocha-logger --save
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

+ mocha-logger@1.0.6
removed 3 packages, updated 1 package and audited 1120 packages in 37.011s

74 packages are looking for funding
  run `npm fund` for details

found 3 low severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
pi@MagicMirror:~/MagicMirror/modules/MMM-Tado $

[sdetweil]

@Wrangler yep, looks like he used a private tado-client module… there is a public node-tado-client , but some of the code would have to change…

sorry…

[Wrangler]

@sdetweil

Thanks for the effort, I wait for a update or try to live with it :confused_face:

[sdetweil]

@Wrangler I added this topic to the issue already open on the node-modules libraries
https://github.com/WouterEekhout/MMM-Tado/issues/8

[Wrangler]

@sdetweil

:thumbs_up:

[WouterEekhout]

Thanks for the feedback. The master-branch has been updated. After git pull, do a npm install.

[Wrangler]

@WouterEekhout

Thanks,

Git pull dit not work.

pi@MagicMirror:~/MagicMirror/modules/MMM-Tado $ git pull
remote: Enumerating objects: 20, done.
remote: Counting objects: 100% (20/20), done.
remote: Compressing objects: 100% (9/9), done.
remote: Total 14 (delta 8), reused 9 (delta 5), pack-reused 0
Unpacking objects: 100% (14/14), done.
From https://github.com/WouterEekhout/MMM-Tado
   7e91b79..59a7fc1  master     -> origin/master
 * [new branch]      2020-june  -> origin/2020-june
Updating 7e91b79..59a7fc1
error: Your local changes to the following files would be overwritten by merge:
	MMM-Tado.js
Please commit your changes or stash them before you merge.
Aborting

But after removing MMM-Tado and reinstalling it works.

Thanks.

[WouterEekhout]

@Wrangler It looks like you’ve made some changes to the MMM-Tado.js file.

Try:

git checkout MMM-Tado.js
git pull

[Wrangler]

@WouterEekhout

Already did a new install of the module, and it is working now.