Other problem on update Pimatic 0.9.35

---

Hi,

I ran the update from the Pimatic web interface and ran into this as result on the update page:

pimatic is up to date.

Found update for pimatic-openweather: current version is 0.9.0, latest version is: 0.9.3

Found update for pimatic-wakeonlan: current version is 0.9.1, latest version is: 0.9.3

pimatic@0.9.35 node_modules/pimatic
├── basic-auth@1.0.4
├── cookie-parser@1.4.3 (cookie-signature@1.0.6, cookie@0.3.1)
├── connect-timeout@1.7.0 (on-headers@1.0.1, ms@0.7.1, debug@2.2.0, http-errors@1.3.1, on-finished@2.3.0)
├── cookie-session@1.2.0 (on-headers@1.0.1, cookies@0.5.0, debug@2.2.0)
├── cross-spawn@4.0.2 (lru-cache@4.0.1, which@1.2.11)
├── body-parser@1.15.2 (content-type@1.0.2, bytes@2.4.0, depd@1.1.0, qs@6.2.0, on-finished@2.3.0, raw-body@2.1.7, http-errors@1.5.0, debug@2.2.0, iconv-lite@0.4.13, type-is@1.6.13)
├── logrotate-stream@0.2.5 (byt@0.1.0, log-rotate@0.2.7, optimist@0.6.1)
├── socket.io@1.5.1 (debug@2.2.0, has-binary@0.1.7, socket.io-parser@2.3.1, socket.io-adapter@0.4.0, engine.io@1.7.2, socket.io-client@1.5.1)
├── jsonlint@1.6.2 (nomnom@1.8.1, JSV@4.0.2)
└── request-promise@2.0.1 (bluebird@2.11.0, request@2.78.0, lodash@4.16.6)

There was an error installing the updates, please check the log.

When looking in the log on my RasPi I see the same text as above in the tree outline.

However Pimatic is running now showing version 0.9.35.
What is the actual error?

Hello,
i also had an error with this update.

The result was the folder

/pimatic-app/node_modules/pimatic

was deleted.
(just good to have this folder in the backup…)

have to serch for the logfile…

mfg
Chris

edit:
just found the

/pimatic-app/npm-debug.log

but i don’t want to post 300 lines code here.

Please check the pimatic.log file for errors

/pimatic-app/pimatic-daemon.log

@chris my /pimatic-app/node_modules/pimatic folder was not deleted.

@mwittig as stated in my posting before ‘pimatic-daemon.log’ also has these lines in it:

pimatic@0.9.35 node_modules/pimatic
├── basic-auth@1.0.4
├── cookie-parser@1.4.3 (cookie-signature@1.0.6, cookie@0.3.1)
├── connect-timeout@1.7.0 (on-headers@1.0.1, ms@0.7.1, debug@2.2.0, http-errors@1.3.1, on-finished@2.3.0)
├── cookie-session@1.2.0 (on-headers@1.0.1, cookies@0.5.0, debug@2.2.0)
├── cross-spawn@4.0.2 (lru-cache@4.0.1, which@1.2.11)
├── body-parser@1.15.2 (content-type@1.0.2, bytes@2.4.0, depd@1.1.0, qs@6.2.0, on-finished@2.3.0, raw-body@2.1.7, http-errors@1.5.0, debug@2.2.0, iconv-lite@0.4.13, type-is@1.6.13)
├── logrotate-stream@0.2.5 (byt@0.1.0, log-rotate@0.2.7, optimist@0.6.1)
├── socket.io@1.5.1 (debug@2.2.0, has-binary@0.1.7, socket.io-parser@2.3.1, socket.io-adapter@0.4.0, engine.io@1.7.2, socket.io-client@1.5.1)
├── jsonlint@1.6.2 (nomnom@1.8.1, JSV@4.0.2)
└── request-promise@2.0.1 (bluebird@2.11.0, request@2.78.0, lodash@4.16.6)

Where other entries are normal in the log.

Hello,
today i was optimize to start the update again…

Remember the last try deleted my /pimatic-app/node_modules/pimatic - folder.
I just had a backup from the 14th of july 2016.
and just copied it back again and it works so far…

But i got this error:

SyntaxError: Unexpected token ILLEGAL
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
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)
at require (internal/module.js:12:17)
at /home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/npm-registry-client/index.js:73:20
at Array.forEach (native)
at CachingRegistryClient.RegClient (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/npm-registry-client/index.js:51:42)
SyntaxError: Unexpected token ILLEGAL
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
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)
at require (internal/module.js:12:17)
at /home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/npm-registry-client/index.js:73:20
at Array.forEach (native)
at CachingRegistryClient.RegClient (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/npm-registry-client/index.js:51:42)
SyntaxError: Unexpected token ILLEGAL
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
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)
at require (internal/module.js:12:17)
at /home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/npm-registry-client/index.js:73:20
at Array.forEach (native)
at CachingRegistryClient.RegClient (/home/pi/pimatic-app/node_modules/pimatic/node_modules/npm/node_modules/npm-registry-client/index.js:51:42)

Hmm just made selective updates like:

cd /home/pi/pimatic-app
sudo npm update --unsafe-perm pimatic-plugin

they were running in an error… but in the gui are no updates available now…

edit:

puh i got it i think…
(sometimes reading helps)
the folder from the backup was from pimatic0.8…
hmm how can i solve this without setup a new system?

edit:
the last lines of the npmdebug.log

25257 error Linux 4.4.26-v7+
25258 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "update" "--unsafe-perm" "pimatic"
25259 error node v4.4.5
25260 error npm  v2.15.5
25261 error code EPEERINVALID
25262 error peerinvalid The package pimatic@0.9.35 does not satisfy its siblings' peerDependencies requirements!
25262 error peerinvalid Peer pimatic-amazing-dash-button@0.9.10 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-bh1750@0.2.0 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-calendar@0.8.0 wants pimatic@0.8.*
25262 error peerinvalid Peer pimatic-cron@0.8.8 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-filebrowser@0.9.0 wants pimatic@0.9.*
25262 error peerinvalid Peer pimatic-fritz@0.5.2 wants pimatic@>0.8.91 <1.0.0
25262 error peerinvalid Peer pimatic-hap@0.9.0 wants pimatic@~0.9.0
25262 error peerinvalid Peer pimatic-homeduino@0.9.11 wants pimatic@0.9.*
25262 error peerinvalid Peer pimatic-iframe@0.2.0 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-links@0.8.6 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-log-reader@0.9.0 wants pimatic@>=0.9.0 <1.0.0
25262 error peerinvalid Peer pimatic-mail@0.8.6 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-max@0.8.18 wants pimatic@>=0.8.31 <1.0.0
25262 error peerinvalid Peer pimatic-mobile-frontend@0.9.11 wants pimatic@0.9.*
25262 error peerinvalid Peer pimatic-mysensors@0.8.34 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-openweather@0.9.3 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-ping@0.9.5 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-pushbullet@0.9.0 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-shell-execute@0.9.7 wants pimatic@0.9.*
25262 error peerinvalid Peer pimatic-sunrise@0.8.7 wants pimatic@>=0.8.0 <1.0.0
25262 error peerinvalid Peer pimatic-sysinfo@0.9.4 wants pimatic@0.9.*
25262 error peerinvalid Peer pimatic-watchdog-unix@0.0.1 wants pimatic@>=0.8.0 <1.0.0
25263 verbose exit [ 1, true ]

Edit:
Ok just installed Pimatic new.
Copied the old config.json into it and let him work…
45 minutes and every was working again…

Database isn’t so maintained for me…

Update of pimatic system kicked my installation already 3 times.

Same like Chris:
Last time I just deleted everything inside the main folder und did a simple "npm install pimatic … " fresh installation,
before start of pimatic I copied my old (and backuped! ) config.json to its right place and then pimatic start.
One hour later everithing was running without further work.

Ofcourse database was deleted/rebuild to an empty state.

Maybe some developer can build something so automate that to a handy GUI backup system?

@DDNRN said in Other problem on update Pimatic 0.9.35:

Ofcourse database was deleted/rebuild to an empty state.

You could have backuped that as well. Just as easy as your config.json.

Maybe for next time

well yes, a backup can be done via some rules. maybe a plugin would get some more users to backup their data.
that plugin could be relativeley open to backup either pimatic or other data / files / dirs and maybe with a time interval and a manual backup button. so you could be able to fastBackup before update
anything. just my 2 cents.

but that is nothing that could not be done by some rules. but i like plugins so if any @developer has any idea go ahead!!
@slix you are still searching for a challenge, here’s your chance

@leader21 said in Other problem on update Pimatic 0.9.35:

@slix you are still searching for a challenge, here’s your chance

I think, this is too hard to start with

An encrypted cloud backup would be nice - maybe along the lines of the following example snippet - https://github.com/google/google-api-nodejs-client/tree/master/samples/drive. Additionally, it would be nice to use gTar to provide incremental backup. This way it would be possible to recover a specific version (along the timeline) of the config.