Is pimatic still alive?

---

I know pimatic has still beta status and is developed by a few people in their spare time. And I find it a great project, easy to setup, easy to us.
Big thanks from my side for all this.

But in last time it seems pimatic isn’t anymore alive.
When I look on github the last commit is already 5 month ago.

Node.js 4.x reached his End-of-life in end of April and this was announced long time ago. But where the development is going on to upgrade pimatic to a newer node.js version?

Also several plugins seems to be not continued anymore.
I opened a issue for pimatic-ble-mi-flora more then one month ago but nothing changed so far.

Same for pimatic-holidays where I even solved the issue my self and made a pull request.

I hope development on pimatic will continue in near future.

@dasmaetthes It is alive. The latest commit has been made two days ago. See https://github.com/pimatic/pimatic/commits/master
Currently, everybody is busy with committed work. Contributions are always welcome.

@dasmaetthes said in Is pimatic still alive?:

Same for pimatic-holidays where I even solved the issue my self and made a pull request.

I briefly reviewed your PR. Can you please briefly describe which problem you experienced with the plugin? Thanks

If a plugin maintainer does not respond to PRs timely you still can insall from your fork. It is not nice, but keeps you going. https://forum.pimatic.org/topic/1114/updated-how-to-install-a-plugin-from-github-using-npm-or-git

Great to hear the development is going on.
It was each 5s checkd if current day is a holiday or not and the result also written to logfile.
I just changed it that it’s checkd only once a day at midnight

@dasmaetthes said in Is pimatic still alive?:

t was each 5s checkd if current day is a holiday or not and the result also written to logfile.
I just changed it that it’s checkd only once a day at midnight

Ah, ok. That makes sense. Note, however, with your change the presence state won’t be set properly after a pimatic restart or a device change. As far as I can see, @_setPresence() should be called in the constructor right after super()