- 20190906, V0.9.53
- Fixed bug: Skip log messages which do not contain meta tags and timeStamp
- Cast null values as part of variable expression to avoid exception “expected … to have numeric value” in case of uninitialized attributes on startup
- Changed cassert dependency to work-around permission issue with npm link
- Added Systemd service wrapper for pimatic. The Initd service wrapper is now deprecated. See also https://pimatic.teamemo.com/Guide/Autostarting
-
pimatic@0.9.53
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
Made the update. Works for me on Stretch and Node.js version 8.16.0.
I really like, that I have no error in the message box after startup what I had always - perfect! Will test later some other stuff…
-
Same for me.
Had always 10 errors. After the MQTT update only 5.
After this update Zero
-
That’s great, guys. Thank you very much for trialing the new versions so quickling and your feedback!
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
I found one thing regarding the error log. I can see this:
But the protocol shows:
The error occurs due to a rule executing error:
21:45:06.372 [pimatic] error: rule bla error executing an action: Error: Command failed: ... -
@Michael-Rudek: Do you have the same behavior as me or did your log show errors during runtime?
-
@ortin No errors , even after rebooting several times…
-
Its the same for me during startup. But I mean if an error occurs during runtime. It will be count, but not shown in the error log.
Error like an not executable script within a rule.Simply make a rule like this
When every 10s then execute "noScript"After a short run some errors are shown in the upper right side:
But the error log shows this, nothing:
-
Yes your right.
The errors are in the log but aren´t shown in the frontend messages -
@mwittig said in pimatic@0.9.53:
Added Systemd service wrapper for pimatic. The Initd service wrapper is now deprecated. See also https://pimatic.teamemo.com/Guide/Autostarting
Btw: I found a mistake in the docu.
The marked text should be pimatic.service I suppose.
-
@ortin said in pimatic@0.9.53:
Btw: I found a mistake in the docu.
Thanks. Fixed
@Michael-Rudek @OrTiN Do you already use the Systemd wrapper with your setup?
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
I have executed the described steps. The last command responsed that service pimatic is already provided, but this is clear due to the running system I already have.
It works for me as far as I can judge. Pimatic restart still works via command
sudo service pimatic start. A full reboot of the raspi as well brings Pimatic automatically back.If this is the way who to test, then it works. Or is it necessary to revoke the “old” way?
-
@mwittig No, i didn´t know, that i have to change something…
-
Hi all,
I updated a couple of days ago and had some trouble restarting Pimatic. Once i got it going again i noticed that the log errors aren´t shown in the frontend messages. I just restarted from the frontend and it seems to ‘hang’ with '/usr/local/bin/pimatic.js restart hogging all my cpu, while tailing pimatic-log says:
00:12:10.599 [pimatic] info: Restarting... 00:12:10.614 [pimatic] info: Flushing database to disk, please wait... 00:12:10.847 [pimatic] info: Flushing database to disk, please wait... Done. 00:12:13.932 [pimatic] info: exiting... 00:12:16.842 2019-09-12 Thursday 00:12:29.814 [pimatic] info: Starting pimatic version 0.9.53 00:12:29.839 [pimatic] info: Node.js version 4.6.2 00:12:29.849 [pimatic] info: OpenSSL version 1.0.2j 00:12:36.663 [pimatic, ppm] info: 2.15.12 00:12:36.731 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8) 00:12:37.719 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.16) 00:12:39.356 [pimatic] info: Loading plugin: "pimatic-sysinfo" (0.9.6) 00:12:39.885 [pimatic] info: Loading plugin: "pimatic-iframe" (0.3.1) 00:12:39.953 [pimatic] info: Loading plugin: "pimatic-metar-weather" (0.9.2)Someone please remind me how to revert to the last version?
-
@fregger assume you haven’t setup the Systemd script as this is only required for new installation. Apart from the code changes in the new release are fairly minimal and I am left in the dark about the cpu hogs you’re reporting. I haven’t seen this in my tests so far, but I’ll keep an eye on this.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@fregger npm install pimatic@0.9.XX
-
Thanx guys.
After the update Pimatic wouldn’t restart properly. That probably screwed up the database. I went back to 0.9.51, deleted/renamed pimatic-database.sqlite and pimatic-database.sqlite-wal and started ‘manually’ from a ‘screen’ session with sudo pimatic.js. That runs fine now. I’ll check later if i can start the daemon again with ‘sudo service pimatic start’.
-
@fregger said in pimatic@0.9.53:
0.9.51
You should better use 0.9.52 if you use rules, as 0.9.51 has a bug inside the expression handler code.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig said in pimatic@0.9.53:
You should better use 0.9.52
Thanx for the tip, got the daemon running again on 09.52 but i still don’t understand why the update didn’t work out in the first place. The update seemed to go well, problems started after clicking restart in the gui after the update.
-
@mwittig said in pimatic@0.9.53:
@Michael-Rudek @OrTiN Do you already use the Systemd wrapper with your setup?
Do you think this could be the reason for the problem with the frontend message box?
