pimatic@0.9.49

---

NOTE: Please backup your database and configuration before performing the update just in case the update breaks.

• 20190627, V0.9.49
  • Added blacklist mechanism to filter-out non-functional or obsolete plugins from list of installable plugins
  • Optimization for Docker
    • Added support for using pm2-docker as an alternative to using the service daemon for docker containers
    • Added experimental install mode to perform sqlite3 installation and generation of JS files as part of the docker image build
  • Updated to sqlite3@4.0.9 for node v12 and Raspbian Buster support
  • Updated documentation reference

@mwittig said in pimatic@0.9.49:

Optimization for Docker

This sounds great!
Does anyone already use a docker and are they willing to share? Do we can an ‘official’ image from Pimatic?

@stokstaart Some users have published their docker builds in the past. See https://hub.docker.com/search?q=pimatic&type=image

Since a few weeks I am working on an “official” docker distribution. I will publish first results soon also to give other @developer’s the opportunity to collaborate on this. One thing I am currently investigating is ways of establishing multi-platform support. The idea is to have single image location for docker images than can run on arm, amd64, and potentially other architectures like arm64.

after updating to this version (from 0.9.48) i get the error described here https://forum.pimatic.org/topic/4671/problem-after-update and pimatic isn’t starting anymore

edit: rpi 3b+, debian stretch, node v4.6.2

Tried to give a solution for that problem in the other thread

https://forum.pimatic.org/topic/4671/problem-after-update

Hi all, also my 2cents here.

After doing now the 0.9.49 update on my Test Rapi (set up by SD card clone with 0.9.48), my installation also chrashed and it reminds me on my problems to set up the Test Raspi from scratch (https://forum.pimatic.org/topic/3146/pimatic-node-8-0).
So it might be that the problems with npm, also doing a fresh installation, have come with that update?

I will now set up again a clone and do not that update again. So if needed I could support with further tests.

In case of need, I stored all the steps and the results for myself in a word doc…

Hello pimatic team.

Despite the fact that you always advise to make a backup of your system before you update, most of us will not do this.
The update to pimatic 0.9.49 was a disaster.
By sheer coincidence, my raspberry broke down, I had a backup and I could restore this backup.

By the way, I was pleasantly surprised at the tone on the forum. Not the cursing and ranting that I often see in other forums when something goes wrong.

Today I saw the update to 0.9.50. Backup made. Update started and …
NO PROBLEMS.

Thanks for the quick recovery.

My compliments.
That may also be said.

Greetings Hans

@hansjeu Thank you very much for the feedback. I am sorry for the inconveniences caused by the v0.9.49 update. With that version I did not bundle the dependencies as some users running on older systems had issues with bundled dependencies which did not match set of installed system libraries. There are also some issues with the old Npm version pimatic uses internally. The legacy will be removed and we hopefully can ditch support for node v4 soon.

As so many users had issues v0.9.50 includes bundled dependencies. Btw, all versions are tested before release, however, these issues did not occur on the test system which however of the different OS/build system/Node versions users have on their system.

Besides the problem with the pimatic updates I noticed larger file system changes on Raspi appears to occasionally break the file system. It happened to me more than once and I can say a corrupted file system can cause all kinds of strange errors. So, we also need a strategy for checking the health of the target system. Possibly a script which performance some basic checks (file-system check, check free space, etc).

Hi all,

I would like to follow @hansjeu and say thank you, that you all always stay patient and continue to support.
I hope that I didn’t paste here too much (raspi-)details of my activities. If so, then please give me a respective feedback. My intend was only to make it maximum transparent which errors occured

Please go ahead with pimatic, because it’s a super application

Regards
Pedder

PS.
As today two additional SD cards arrived, I will also test a fresh installation with 0.9.50 from scratch within the next days.

@mwittig Looking forward to your Container! Right now i am using Debian as main image and building Pimatic on that. I found several containers on the HUB but they were either not updated for years or i found them very unstable on my synology (not booting or other issues)

I you are looking for people to test your container i would like to volunteer!! (I think docker is something where you can test your setup in a very easy-to-setup manner…)

me too. i’m actually struggling in writing my own dockerfile… but i don’t know, how good it will be…

@quotschmacher good news! I got the petschni/pimatic container running on my synology, if you need some help you can contact me here!

@Stokstaart thanks. during the weekend I got my container running, too on a pi.i adopted some dockerfile from dockerhub for my needs.