Pimatic doesn't start anymore after update

---

After an update attempt, I get the following error and thus cannot start pimatic anymore:

pi@raspberrypi:~/pimatic-app $ sudo ./node_modules/pimatic/pimatic.js
module.js:327
    throw err;
    ^

Error: Cannot find module 'fs.extra'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic/coffee-cache.js:27:14)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)

Please help

Already figured out a workaround:

• copy node_modules to backup dir
• restart pimatic

If there are problems, you probably can solve them step by step. I myself had some issues with a couple of variables that I had to remove.

Hey,
I have the same problem. How do I do that, i am a pimatic phyton beginner.

VG

Ingo

I got this during the update process:

npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)

Error: Cannot find module './dir-reader.js'

at Function.Module._resolveFilename (module.js:325:15)

at Function.Module._load (module.js:276:25)

at Module.require (module.js:353:17)

at require (internal/module.js:12:17)

at Packer.Reader (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream/lib/reader.js:53:19)

at Packer.DirReader (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream/lib/dir-reader.js:35:10)

at Packer.IgnoreReader (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/ignore.js:68:13)

at new Packer (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream-npm/fstream-npm.js:23:10)

at pack_ (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/lib/utils/tar.js:48:3)

at Object.pack (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/lib/utils/tar.js:43:5)

Error: Cannot find module './dir-reader.js'

at Function.Module._resolveFilename (module.js:325:15)

at Function.Module._load (module.js:276:25)

at Module.require (module.js:353:17)

at require (internal/module.js:12:17)

at Packer.Reader (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream/lib/reader.js:53:19)

at Packer.DirReader (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream/lib/dir-reader.js:35:10)

at Packer.IgnoreReader (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream-npm/node_modules/fstream-ignore/ignore.js:68:13)

at new Packer (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/fstream-npm/fstream-npm.js:23:10)

at pack_ (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/lib/utils/tar.js:48:3)

at Object.pack (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/lib/utils/tar.js:43:5)

npm ERR! cb() never called!```



'Updates were successful. Please restart pimatic.'

Should i be worried?

Hi,
look here!
Pimatic release 0.9.43

There are multiple topics about errors after the latest update.
The fastest way to fix this atm is to copy your config.json, remove or copy you pimatic folder and reinstall pimatic.

cd /home/pi
npm install pimatic --prefix pimatic-app --production

Thanx guys! I ended up applying this solution: https://forum.pimatic.org/topic/4340/released-pimatic-0-9-43/19

That got things going again.

@xs400 I moved the node_modules to a backup dir by something like

mv node_modules node_modules_backup

Then i just restarted pimatic. Pimatic now starts redownloading/installing all components again. I had one issue with a variable and a plugin, which I had to disable in the config file. (Make sure to make a copy of the config file, because pimatic will overwrite it.)

For me this worked. I think that the solution provided by @incmve will do the same.