- 20190414, V0.9.48
- Added config extension for Shutter position labels
- Fixed creation of variables for new attributes on changed (edited) device
- Fixed catch statement missing error parameter on device initialization
- Updated dependencies
-
pimatic@0.9.48
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Good morning,
update process running and pimatic is running.
Nice day.Pimatic, my hobby.
-
Update was successful, but how to interpret this?
I know my node version is to low but is this ok for pimatic?>> https://forum.pimatic.org/post/35740
to which node version is it safe to update? currently I am on 4.9.1>> https://forum.pimatic.org/post/35743
-
@00lex said in pimatic@0.9.48:
but how to interpret this?
That’s OK for now. punycode and har-validate declare engine requirements for node.js v6, but the code runs fine on v4. Hopefully, we can leave v4 behind very soon.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
great. thanks!
-
Hey guys,
maybe it is only on my system, but I’ve recognized much more memory usage with the new version. Before the update the system run with round about 300-350MB now it is 900-950MB. Somebody else here who observed the same?#EDIT: I think it could be simple pimatic-sysinfo@0.9.5, the new version pimatic-sysinfo@0.9.6 will get back to the previous values.
-
@ortin Which tool/plugin do you use to obtain memory usage info?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Sysinfo. I edit my last post. Haven’t seen the update…
*EDIT: Because I start my question here I will proceed here, hope this is okay. With 0.9.6 I am back on the old values. THX
-
Hello and many thanks for all the efforts to @mwittig and all the other helpers. I have rebuilt the whole on a test Raspberry.
New Raspian version
2019-04-08-raspbian-stretch-lite.img,
pimatic0.9.48
nodev8.16.0
npm6.4.1
All plugins are now up to date, as it stands today.I first loaded the SD card with Raspbian, then installed Node v8 with npm v6 on it, and then installed latest pimatic.
Then copy a part of my old config (only the plugin part) into the new config.After some privat problems with links, pimatic ran too.
Unfortunately there are still a lot of error messages in the log.like this at start:
Unhandled rejection Error: Bad request at Object.ensureErrorObject (/home/pi/pimatic-app/node_modules/bluebird/js/main/util.js:261:20) at Promise._rejectUncheckedCheckError (/home/pi/pimatic-app/node_modules/bluebird/js/main/promise.js:660:22) at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:566:21) at Promise._settlePromiseCtx (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:606:10) at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:142:12) at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:9) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:147:5) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5) Unhandled rejection Error: Bad request at Object.ensureErrorObject (/home/pi/pimatic-app/node_modules/bluebird/js/main/util.js:261:20) at Promise._rejectUncheckedCheckError (/home/pi/pimatic-app/node_modules/bluebird/js/main/promise.js:660:22) at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:566:21) at Promise._settlePromiseCtx (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:606:10) at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:142:12) at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:9) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:147:5) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5) Unhandled rejection Error: Bad request at Object.ensureErrorObject (/home/pi/pimatic-app/node_modules/bluebird/js/main/util.js:261:20) at Promise._rejectUncheckedCheckError (/home/pi/pimatic-app/node_modules/bluebird/js/main/promise.js:660:22) at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:566:21) at Promise._settlePromiseCtx (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:606:10) at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:142:12) at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:9) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:147:5) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5) Unhandled rejection Error: Bad request at Object.ensureErrorObject (/home/pi/pimatic-app/node_modules/bluebird/js/main/util.js:261:20) at Promise._rejectUncheckedCheckError (/home/pi/pimatic-app/node_modules/bluebird/js/main/promise.js:660:22) at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:566:21) at Promise._settlePromiseCtx (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/promise.js:606:10) at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:142:12) at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:131:9) at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:147:5) at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5)During normal operation, this keeps coming back:
Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn curl -s http://weather.yahooapis.com/forecastrss?w=12832969|grep astronomy| awk -F\" '{print $2}' ENOENT Unhandled rejection Error: spawn curl -s http://weather.yahooapis.com/forecastrss?w=12832969|grep astronomy| awk -F\" '{print $4}' ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn sudo bash /home/pi/scripte/uptime.sh ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn date +%H:%M ENOENT Unhandled rejection Error: spawn curl -s http://weather.yahooapis.com/forecastrss?w=12832969|grep astronomy| awk -F\" '{print $2}' ENOENT Unhandled rejection Error: spawn curl -s http://weather.yahooapis.com/forecastrss?w=12832969|grep astronomy| awk -F\" '{print $4}' ENOENTBut the system runs for now, and that’s good.
Edit:
Unfortunately some rules have also been overruled. Some devices seem to be gone. I have to take care of them in detail again.
So first back to the smoothly running Raspberry."Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
-
I did the upgrade to 0.9.48 as well and it worked fine.
I had again a modified sysinfo@0.9.5 with my own systemUptimeDHM and pimaticUptimeDHM. The upgrade went fine to sysinfo@0.9.6.
Of course the device did not work, but pimatic started nicely this time and did not hang on the the incorrect device.
So I removed my systemUptimeDHM and pimaticuptimeDHM from the device and replaced it with the systemUptime and pimaticUptime, and modified the xAtrributes according the attribute Formats now available in the pimatic-mobile-frontend@0.9.15.Excellent work: Thanks.
And another thanks for making the error capturing more resilient, so pimatic doesn’t stop on unknown or “incorrect” configured devices. -
I’ve been on Stretch now for quite a while and have been postponing updating Pimatic because 0.9.43 was very stable for me. Yesterday I finally updated everything. During the updates i saw a few warnings:
npm WARN engine har-validator@5.1.3: wanted: {“node”:">=6"} (current: {“node”:“4.6.2”,“npm”:“2.15.12”})
npm WARN engine punycode@2.1.1: wanted: {“node”:">=6"} (current: {“node”:“4.6.2”,“npm”:“2.15.12”})
npm WARN engine node-mbed-dtls@2.4.4: wanted: {“node”:">=5.0.0"} (current: {“node”:“4.6.2”,“npm”:“2.15.12”})Everything runs smoothly, thanks for the excellent work!
The only thing that doesn’t seem to work anymore is PimaticDroid.
