pimatic@0.9.53

---

@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.

@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.

@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?

Pimatic from 0.9.51 updated to 0.9.53 with:

mqtt 0.9.13
milight-reloaded 0.9.18
pushbullet 0.9.0
sunrise 0.9.3
yamaha-avr 0.9.4

works perfect.
Thanks all for your great work!

@tobias-riesemann Excellent. Thanks for your feedback and for reporting!

Did you experience any anomalies when you restarted pimatic? I am just asking as some users on this thread experienced problems (CPU hogs). Which version of Node.js do you have installed, btw.?

Hi, i noticed no uncommon CPU issues whether during startup nore after pimatic is running on my Raspberry 1B.

CPU is about:
top - 09:19:21 up 32 days, 16:37, 1 user, load average: 0,19, 0,07, 0,07

Currently i’m using node v4.8.4

@tobias-riesemann said in pimatic@0.9.53:

works perfect.
Thanks all for your great work!

Does the front end error log works for you?

I also updated to 9.53. It seems (almost) everything to work. But I can also confirm the problem with the log display.

There is nothing displayed.

Sorry, for the late reply. As i now can see, the error log is empty.

@mwittig: Any idea? Do you can reproduce this in your environment? If not what do you need?

@mwittig: Do you haven’t any clue?

Hi @mwittig,
I today updated from 0.9.48 to 0.9.53.
It worked very well, without producing any errors Thanks for that!
My config: Raspi 3B Node: v10.15.3

As I always do the updates from the frontend, I did at the same time the updates for:
pimatic-mobil-frontend (0.9.15 to 0.9.16)
pimatic-raspbee (0.0.10 to 0.1.5)
Wouldn’t it be a good idea to have there the possibility not to do all open updates at the same time?
I’m asking that in reference of maybe occuring errors while updating.
Doing the updates not all at the same time, might help to identify errors.
What do you think?

Thanks again for the super quality
Pedder

https://forum.pimatic.org/topic/4728/separated-update-feature-for-plugins-and-core-releases
Vote!!!

Done

Hey Guys…

i dont if its Pimatic lasted update or Module but i see that everytime i start / restart Pimatic it will created a file in Root with 0bytes called “0”.

(i would upload a Pic of it but the Forum says i dont have permission to upload ?!? )

Someone knows for what this file is and why it will be created?

@mwittig Hi Marcus, been awhile. Just got back to Pimatic, although my time will be limited. I have submitted a pull on Github for Pimatic core to fix Log Messages not shown / disappearing #1131.

@OrTiN and others: until a new release is available this can be hacked by changing <pimatic-app>/node_modules/pimatic/lib/database.coffee:

line 122:
if meta?.timeStamp and meta.tags?
to:
if meta?.timestamp and meta.tags?

The uppercase S in timeStamp should be lowercase. After reboot all is well.

Kind regards,

Dan

Hey Dan, nice to see you back here!!!