Yes it is a manual installation. But you have been to fast and u was to slow with typing. You need to do that in the pimatic-app folder
-
Pimatic won't run
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
ok.
I’m trying to understand all the commands and where to start them.
I would like to have all Pimatic sources in the pimatic-app folder to keep all clearI perfomed now in the pimatic-app folder with the same output.
-
Next try
Again in the /home/pi/pimatic-app folder
sudo npm install sqlite3 --unsafe-perm
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
sudo node /home/pi/pimatic-app/node_modules/pimatic/pimatic.js
started and all plugins seem to get started now.will this process end?
I mean do I have to wait for the prompt to come back ik the command window? -
OK nice to hear!
this is now running until you stop it with ctrl+c
You now should be able to run pimatic with the usual commands like sudo service pimatic startpimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
@leader21 Thanks! I can start the process now. Also connected to my browser.
However when I choose to debug (to see my MySensors nodes and Homeduino sensors) I see no info.
My PIRs seem to function and also a Homeduino Temp sensor.
However a MySensors Temp sensor and another Homeduine Temp sensor have ‘unknown’ values.EDIT: I repowered them and now all is working!!!
-
One of the problems of this install is that it does root base installs in a user directory instead of some system folder. That is not a “nice” approach so to say and should be improved “some time” in one of the next versions. It should either be a user install, or a system install in some system folder like
/usr/local
.Anyway:
If pi is the owner (like in/home/pi
) I always do, in/home/pi
asudo chown -R pi:pi pimatic-app
, which will change ownership recursively for that folder structure/home/pi/pimatic-app
to the “real” owner pi.
root will always be able to write to that folder structure anyway in case of (plugin) updates. -
@Harry-van-der-Wolf said in Pimatic won't run:
One of the problems of this install is that it does root base installs in a user directory instead of some system folder. That is not a “nice” approach so to say and should be improved “some time” in one of the next versions. It should either be a user install, or a system install in some system folder like
/usr/local
.Anyway:
If pi is the owner (like in/home/pi
) I always do, in/home/pi
asudo chown -R pi:pi pimatic-app
, which will change ownership recursively for that folder structure/home/pi/pimatic-app
to the “real” owner pi.
root will always be able to write to that folder structure anyway in case of (plugin) updates.That’s what I also did before. In this case I hope to avoid updates to malfunction due to permission issues.
-
@Petjepet said in Pimatic won't run:
One of the problems of this install is that it does root base installs in a user directory instead of some system folder. That is not a “nice” approach so to say and should be improved “some time” in one of the next versions. It should either be a user install, or a system install in some system folder like /usr/local.
The problem is that the pimatic process has to run with root privileges as some plugin require it. Maybe it is possible to switch the user when packages are installed.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig said in Pimatic won't run:
The problem is that the pimatic process has to run with root privileges as some plugin require it. Maybe it is possible to switch the user when packages are installed.
I know. I have already been thinking about it.
As such it is no problem at all that it runs as root. I even prefer it that way. (Allmost) All daemons run under root or some special dedicated user and not in user space.
However, in this case I would have expected to have it run in/usr/local
.One of the install steps is
sudo mkdir pimatic-app && sudo npm install pimatic --prefix pimatic-app --production
from the users home folder/home/pi
(in most cases). For me it is running in/home/harryvanderwolf
anyway as I don’t use user pi.
If that would becd /usr/local && sudo mkdir pimatic-app && sudo npm install pimatic --prefix pimatic-app --production
, it would be a nice root install, be run from /usr/local and the daemon would also run from a default system path.
When I’m back this weekend I will try that with my (backup) Bananapi (It is already running 0.9 in/opt/pimatic/pimatic-app
as I used that as test machine and didn’t want it in my home folder either)