Thanks, I tried to merge the new database with the old one, without luck --> I am not quite a database specialist. Though then I just replaced the new database with my old one and stuff works fine. Lost the last few days, but that is far better than losing an entire year
Really love pimatic 0.9 by the way, I seems to react a lot faster and the new configuration options via the GUI are great!
-
Questions about the release of v0.9
-
@leader21
Yes the issue is still alive.Have found another info to npm…
See the picture below.
Update-issueMit freundlichen Grüßen
Chris -
@Chris You mention “Because I can access my system via Internet the error is a bit curious…”.
No it is not. If you can access your system from internet it means that you either- connect to the ip-address of your router, which will be forwarded and will always works if your router is correctly configured
- or to a domain name which will works if dns is correctly configured on that pc that you use to access your pimatic server.
That doesn’t mean dns is correctly configured on your pimatic box itself.
Try to do a ping from the command line from your pimatic box itself, likeping api.pimatic.org
and see if that works.
If that works there is indeed a strange issue with pimatic.If that ping doesn’t work I assume your pimatic server has a static ip-address but you forgot to configure the dns servers on your pimatic box which will take care of resolving the api.pimatic.org address from your pimatic box.
If you use a static ip please check your
/etc/resolv.conf
for correct dns servers. You can always enter in that resolv.conf file the following serversnameserver 8.8.8.8 nameserver 8.8.4.4
which are the Google dns servers and which are actually a huge number of dns servers so there are always hundreds of them up and running.
-
@chris check harry’s suggestion above.
If it fails I will take it to the team.pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
Hello @Harry-van-der-Wolf and @leader21
yes ping the api works.
i get this back.PING api.pimatic.org (37.120.167.13) 56(84) bytes of data. 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=2 ttl=57 time=21.4 ms 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=3 ttl=57 time=28.1 ms 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=4 ttl=57 time=21.6 ms 64 bytes from v22016053588334358.bestsrv.de (37.120.167.13): icmp_seq=5 ttl=57 time=21.5 ms
my network looks like the following.
Here i have a Windows Exchange Server wich is the dhcp-server and a fritzbox wich is the gateway.
In the DHCP server a made a reservation for the IP of the Raspberry.
So that he always gets the right/same IP.mfg
Chris -
Hi there,
I’m experiencing problems when updating to the latest version of pimatic by using the updates-page in pimatic.
the
/home/pi/pimatic-app/node_modules/pimatic
folder is gone now, so I tried to reinstall it:
but without any luck…Of course I can rm the complete pimatic-app folder and do a complete reinstall, but there should be an easier solution I think.
Any idea how to fix my installation?
-
@leader21 @pimatic-team
Updates arme working again…Mit freundlichen Grüßen
Chris -
Hi,
I have also tried to update via the update page and appeared to be unsuccessfull.
I like to go back to my previous version, Could use some help with this one. It looks like
node.js needs an update as well. -
@mcblack
Pls. be more precise. What did you try to update and what’s the error message from the log?pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@leader21 I did an update of plugins and pimatic by means of the web interface just as I was used to. But now received errors and pimatic is not starting anymore. When tried to start up in debug mode received message wrong version of node.js and need to upgrade to > 4.0.
npm debug log is to large to post here find below part of it
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/local/bin/node’,
1 verbose cli ‘/usr/local/bin/npm’,
1 verbose cli ‘update’,
1 verbose cli ‘pimatic-sunrise’ ]
2 info using npm@1.3.21
3 info using node@v0.10.24
4 verbose url raw pimatic-sunrise/latest
5 verbose url resolving [ ‘https://registry.npmjs.org/’, ‘./pimatic-sunrise/latest’ ]
6 verbose url resolved https://registry.npmjs.org/pimatic-sunrise/latest
7 info trying registry request attempt 1 at 17:21:35
8 verbose etag “2ZP3UU8Y2G9FI227SATN5I4HU"
9 http GET https://registry.npmjs.org/pimatic-sunrise/latest
10 http 200 https://registry.npmjs.org/pimatic-sunrise/latest
11 silly registry.get cb [ 200,
11 silly registry.get { server: ‘CouchDB/1.5.0 (Erlang OTP/R16B03)’,
11 silly registry.get etag: ‘“8S67OSREFRSA79FKBWKLF2SNL”’,
11 silly registry.get ‘content-type’: ‘application/json’,
11 silly registry.get ‘cache-control’: ‘max-age=300’,
11 silly registry.get ‘content-length’: ‘1373’,
11 silly registry.get ‘accept-ranges’: ‘bytes’,
11 silly registry.get date: ‘Mon, 27 Jun 2016 15:21:38 GMT’,
11 silly registry.get via: ‘1.1 varnish’,
11 silly registry.get age: ‘0’,
11 silly registry.get connection: ‘keep-alive’,
11 silly registry.get ‘x-served-by’: ‘cache-ams4125-AMS’,
11 silly registry.get ‘x-cache’: ‘MISS’,
11 silly registry.get ‘x-cache-hits’: ‘0’,
11 silly registry.get ‘x-timer’: ‘S1467040898.531637,VS0,VE381’,
11 silly registry.get vary: ‘Accept-Encoding’ } ]
12 verbose cache add [ ‘pimatic-sunrise’, '’ ]
13 verbose cache add name=“pimatic-sunrise” spec="” args=[“pimatic-sunrise”,""]
14 verbose parsed url { protocol: null,
14 verbose parsed url slashes: null,
14 verbose parsed url auth: null,
14 verbose parsed url host: null,
14 verbose parsed url port: null,
14 verbose parsed url hostname: null,
14 verbose parsed url hash: null,
14 verbose parsed url search: null,
14 verbose parsed url query: null,
14 verbose parsed url pathname: '’,
14 verbose parsed url path: ‘’,
14 verbose parsed url href: '’ }
15 verbose addNamed [ ‘pimatic-sunrise’, ‘’ ]
16 verbose addNamed [ null, '’ ]
17 silly lockFile 97efbc52-pimatic-sunrise pimatic-sunrise@*
18 verbose lock pimatic-sunrise@* /usr/local/pimatic-app/.npm/97efbc52-pimatic-sunrise.lock
19 silly addNameRange { name: ‘pimatic-sunrise’, range: ‘’, hasData: false }
20 verbose url raw pimatic-sunrise
21 verbose url resolving [ ‘https://registry.npmjs.org/’, ‘./pimatic-sunrise’ ]
22 verbose url resolved https://registry.npmjs.org/pimatic-sunrise
23 info trying registry request attempt 1 at 17:22:00
24 verbose etag "2ZP3UU8Y2G9FI227SATN5I4HU"
25 http GET https://registry.npmjs.org/pimatic-sunrise
26 http 200 https://registry.npmjs.org/pimatic-sunrise
27 silly registry.get cb [ 200,
27 silly registry.get { server: ‘CouchDB/1.5.0 (Erlang OTP/R16B03)’,
27 silly registry.get etag: ‘“8S67OSREFRSA79FKBWKLF2SNL”’,
27 silly registry.get ‘content-type’: ‘application/json’,
27 silly registry.get ‘cache-control’: ‘max-age=300’,
27 silly registry.get ‘content-length’: ‘17766’,
27 silly registry.get ‘accept-ranges’: ‘bytes’,
27 silly registry.get date: ‘Mon, 27 Jun 2016 15:22:09 GMT’,
27 silly registry.get via: ‘1.1 varnish’,
27 silly registry.get age: ‘0’,
27 silly registry.get connection: ‘keep-alive’,
27 silly registry.get ‘x-served-by’: ‘cache-ams4136-AMS’,
27 silly registry.get ‘x-cache’: ‘MISS’,
27 silly registry.get ‘x-cache-hits’: ‘0’,
27 silly registry.get ‘x-timer’: ‘S1467040928.864141,VS0,VE479’,
27 silly registry.get vary: ‘Accept-Encoding’ } ]
28 silly addNameRange number 2 { name: ‘pimatic-sunrise’, range: '’, hasData: true }
29 silly addNameRange versions [ ‘pimatic-sunrise’,
29 silly addNameRange [ ‘0.7.0’,
29 silly addNameRange ‘0.7.1’,
29 silly addNameRange ‘0.7.2’,
29 silly addNameRange ‘0.7.3’,
29 silly addNameRange ‘0.8.0’,
29 silly addNameRange ‘0.8.1’,
29 silly addNameRange ‘0.8.2’,
29 silly addNameRange ‘0.8.3’,
29 silly addNameRange ‘0.8.4’,
29 silly addNameRange ‘0.8.5’,
29 silly addNameRange ‘0.8.6’,
29 silly addNameRange ‘0.8.7’ ] ]
30 verbose addNamed [ ‘pimatic-sunrise’, ‘0.8.7’ ]
31 verbose addNamed [ ‘0.8.7’, ‘0.8.7’ ]
32 silly lockFile 9d3ec49a-pimatic-sunrise-0-8-7 pimatic-sunrise@0.8.7
33 verbose lock pimatic-sunrise@0.8.7 /usr/local/pimatic-app/.npm/9d3ec49a-pimatic-sunrise-0-8-7.lock
34 silly lockFile 48503dae-unrise-pimatic-sunrise-0-8-7-tgz https://registry.npmjs.org/pimatic-sunrise/-/pimatic-sunrise-0.8.7.tgz
35 verbose lock https://registry.npmjs.org/pimatic-sunrise/-/pimatic-sunrise-0.8.7.tgz /usr/local/pimatic-app/.npm/48503dae-unrise-pimatic-sunrise-0-8-7-tgz.lock
36 verbose addRemoteTarball [ ‘https://registry.npmjs.org/pimatic-sunrise/-/pimatic-sunrise-0.8.7.tgz’,
36 verbose addRemoteTarball ‘133d34f81e65ddcdedb00b73971eb1a031c3683f’ ]
37 info retry fetch attempt 1 at 17:22:23
38 verbose fetch to= /usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/tmp.tgz
39 http GET https://registry.npmjs.org/pimatic-sunrise/-/pimatic-sunrise-0.8.7.tgz
40 http 200 https://registry.npmjs.org/pimatic-sunrise/-/pimatic-sunrise-0.8.7.tgz
41 verbose tar unpack /usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/tmp.tgz
42 silly lockFile 8cb7307a-39936-0-8368265572935343-package tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package
43 verbose lock tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package /usr/local/pimatic-app/.npm/8cb7307a-39936-0-8368265572935343-package.lock
44 silly lockFile 9b224abd-39936-0-8368265572935343-tmp-tgz tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/tmp.tgz
45 verbose lock tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/tmp.tgz /usr/local/pimatic-app/.npm/9b224abd-39936-0-8368265572935343-tmp-tgz.lock
46 silly gunzTarPerm modes [ ‘755’, ‘644’ ]
47 silly gunzTarPerm extractEntry package.json
48 silly gunzTarPerm extractEntry README.md
49 silly gunzTarPerm extractEntry LICENSE
50 silly gunzTarPerm extractEntry device-config-schema.coffee
51 silly gunzTarPerm extractEntry sunrise-config-schema.coffee
52 silly gunzTarPerm extractEntry sunrise.coffee
53 silly lockFile 8cb7307a-39936-0-8368265572935343-package tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package
54 silly lockFile 8cb7307a-39936-0-8368265572935343-package tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package
55 silly lockFile 9b224abd-39936-0-8368265572935343-tmp-tgz tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/tmp.tgz
56 silly lockFile 9b224abd-39936-0-8368265572935343-tmp-tgz tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/tmp.tgz
57 verbose tar pack [ ‘/usr/local/pimatic-app/.npm/pimatic-sunrise/0.8.7/package.tgz’,
57 verbose tar pack ‘/usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package’ ]
58 verbose tarball /usr/local/pimatic-app/.npm/pimatic-sunrise/0.8.7/package.tgz
59 verbose folder /usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package
60 silly lockFile 8cb7307a-39936-0-8368265572935343-package tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package
61 verbose lock tar:///usr/local/pimatic-app/tmp/npm-25915-N3NTBi8K/1467040939936-0.8368265572935343/package /usr/local/pimatic-app/.npm/8cb7307a-39936-0-8368265572935343-package.lock
62 silly lockFile 6e3a5cb9-imatic-sunrise-0-8-7-package-tgz tar:///usr/local/pimatic-app/.npm/pimatic-sunrise/0.8.7/package.tgz
63 verbose lock tar:///usr/local/pimatic-app/.npm/pimatic- -
@mcblack said in Questions about the release of v0.9:
2 info using npm@1.3.21
3 info using node@v0.10.24You still have an outdated version of nodeJS installed. See the following post for further instructions. https://forum.pimatic.org/topic/1964/pimatic-v0-9-autostart-not-functioning/13
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig I did what you have suggested, but appeared also not successful,
Output from below command:pi@raspberrypi /usr/local/bin $ node --version
Segmentatiefout -
@mcblack said in Questions about the release of v0.9:
Segmentatiefout
Supposedly, this is a “segmenation fault”. Therefore, my suggestion is to remove nodeJS completely and install again! Possibly, you should start with an up-to-date Raspbian Jessie image (see https://www.raspberrypi.org/downloads/raspbian/). If you have an older system version you can upgrade the system to latest version. By all means make sure you have the latest version of “build-essential” installed. Make sure to pick the right nodeJS version for your platform, see the installation guide for details, https://pimatic.org/guide/getting-started/installation/
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig I have upgraded to Jessie successfully and reinstall of node.js but still recieving the segmentation failure.
-
@mcblack Segmentation fault is gone now. I used the intalation files for arm7 instead of arm6. So that proble is solved. whe starting pimatic received the following error:
11:35:34.029 2016-06-30 Thursday
11:36:01.617 [pimatic] Starting pimatic version 0.9.28
Knex: run
$ npm install sqlite3 --save
Error: Cannot find module '/usr/local/pimatic-app/node_modules/sqlite3/lib/binding/node-v46-linux-arm/node_sqlite3.node’
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> (/usr/local/pimatic-app/node_modules/sqlite3/lib/sqlite3.js:4:15)
at Module._compile (module.js:409:26)
at Object.Module._extensions…js (module.js:416:10)
at Module.load (/usr/local/pimatic-app/node_modules/pimatic/node_modules/coffee-script/lib/coffee-script/register.js:45:36)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Client._driver (…/…/…/src/dialects/sqlite3/index.js:37:12)
at Client.initializeDriver (…/src/client.js:153:26)
at Client (…/src/client.js:36:10)
at Client_SQLite3 (…/…/…/src/dialects/sqlite3/index.js:19:10)
at new Client (…/…/src/util/make-client.js:15:18)
at Knex (…/src/index.js:37:19)
at /usr/local/pimatic-app/node_modules/pimatic/lib/database.coffee:71:17
at tryCatcher (/usr/local/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/local/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:503:31)
at Promise._settlePromise (/usr/local/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:560:18)
at Promise._settlePromiseCtx (/usr/local/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:597:10)
at Async._drainQueue (/usr/local/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:12)
at Async._drainQueues (/usr/local/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:136:10)
at Immediate.Async.drainQueues [as _onImmediate] (/usr/local/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:16:14)
at processImmediate [as _immediateCallback] (timers.js:383:17) -
@mcblack
Install sqlite like that
sudo npm install sqlite3 --unsafe-perm
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@leader21 I did a new install following:
Update process from v0.8 to v0.9First remove the old nodejs version (see above), then install the latest node4.x.x release (see checkist above) then go ahead :
sudo service pimatic stop cd /home/pi sudo mv pimatic-app pimatic-v08 sudo mkdir pimatic-app && sudo npm install pimatic --prefix pimatic-app --production sudo cp pimatic-v08/config.json pimatic-app/config.json sudo pimatic.js
And appeared succesful, many thanks for getting me on the right track.
One question:
Can i remove the first install in /usr/local/ by removing the pimatic-app dir
as the install is now in my /home/pi/pimatic-app/ -
Nice to hear. You can remove the first installation, that’s ok.
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
I would like to update to v0.9 but it seems that pushover is still not working (see spreadsheet) and its important to me.
Does anyone know if @sweetpi is working on an update?regards
-
@benbeton said in Questions about the release of v0.9:
Does anyone know if @sweetpi is working on an update?
I have updated it yesterday. There is a new version now ready for pimatic 0.9
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law