osmc@DodOsmc:~$ sudo pimatic.js
sudo: pimatic.js: command not found
osmc@DodOsmc:~$
I will do it complete new, if there are already probs, i will report. I think i do so much wrong ^^
[Solved] Installing Pimatic 0.9 @OSMC?
osmc@DodOsmc:~$ sudo pimatic.js
sudo: pimatic.js: command not found
osmc@DodOsmc:~$
I will do it complete new, if there are already probs, i will report. I think i do so much wrong ^^
no wait!
go to /home/osmc/pimatic/node_modules/pimatic
now do sudo node pimatic.js
this should start pimatic, thats not a problem!!
pimatic has not been linked, you haven’t done the whole installation process right now i guess.
go to the above folder and do sudo npm link
now you can do the last steps to get the autostart working
wget https://raw.githubusercontent.com/pimatic/pimatic/v0.9.x/install/pimatic-init-d
sudo cp pimatic-init-d /etc/init.d/pimatic
sudo chmod +x /etc/init.d/pimatic
sudo chown root:root /etc/init.d/pimatic
sudo update-rc.d pimatic defaults
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebook
make it so !
Its the same Problem again with homeduino i confugure it, after reboot process is dead
How can i install ESPimaticRF?
Or can somebody send me a complete image Datei what is correct?
@Dodo88 I’ll try to reproduce the case, i.e, I’ll create a test setup using OSMC
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Thx thats awesome!
Here’s the error log with sudo pimatic.js
osmc@DodOsmc:~/pimatic-app$ sudo pimatic.js
12:09:35.507 2016-11-17 Thursday
12:09:45.461 [pimatic] Starting pimatic version 0.9.36
12:09:49.674 [pimatic, ppm] 2.15.9
12:09:49.757 [pimatic] Loading plugin: “pimatic-cron” (0.8.8)
12:09:50.605 [pimatic] Loading plugin: “pimatic-mobile-frontend” (0.9.11)
12:09:51.860 [pimatic] Loading plugin: “pimatic-homeduino” (0.9.11)
12:09:53.424 [pimatic-cron] the time is: Thu Nov 17 2016 12:09:53 GMT+0100 (CET)
12:09:54.813 [pimatic] A uncaught exception occured: Error: spawn /home/osmc/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/bin/vhduino ENOENT
12:09:54.813 [pimatic]> at exports._errnoException (util.js:911:11)
12:09:54.813 [pimatic]> at Process.ChildProcess._handle.onexit (internal/child_process.js:189:32)
12:09:54.813 [pimatic]> at onErrorNT (internal/child_process.js:355:16)
12:09:54.813 [pimatic]> at nextTickCallbackWith2Args (node.js:458:9)
12:09:54.813 [pimatic]> at process._tickCallback (node.js:372:17)
12:09:54.813 [pimatic]> This is most probably a bug in pimatic or in a module, please report it!
12:09:54.820 [pimatic] exiting…
osmc@DodOsmc:~/pimatic-app$
@Dodo88 I was able to reproduce the problem. I digged a little bit deeper into this and found the problem is caused by a non-standard location of ld-linux.so.3. This can be resolved by creating the missing link as follows:
sudo ln -s /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib/ld-linux.so.3
Then restart pimatic using the service wrapper. i.e., sudo service pimatic restart
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Wouldn’t it be better to add /lib/arm-linux-gnueabihf/
to the Path? Maybe other library which will be needed at some point in time will be in the “wrong” location too.
Ideally creat a pull request for OSMC
Just like the bin directory for OSMC is added here:
https://github.com/osmc/osmc/blob/528c5a001d0f6e3b7b3dc70924e74e37b605515d/package/base-files-osmc/files/etc/profile.d/100-add-sbin.sh
@thex said in Installing Pimatic 0.9 @OSMC?:
Wouldn’t it be better to add /lib/arm-linux-gnueabihf/to the Path
Tried this, but it does not seem to work. I have tried
export PATH=$PATH:/lib/arm-linux-gnueabihf/
and
export LD_LIBRARY_PATH=/lib/arm-linux-gnueabihf/
Please advise further if you know how this should be solved. I am not sure how the path for the ELF interpreter is resolved. The environment variables above does not seem to apply. Meanwhile I have created an issue at https://github.com/osmc/osmc/issues/339
Probably related to the matter: https://wiki.debian.org/Multiarch/LibraryPathOverview#ELF_interpreter-1
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
@mwittig
pimatic runs as a service. It doesn’t help by exporting something from your own shell.
If you want to do it system wide you could add it to the PATH in /etc/profile
, which is the simplest solution but not the right solution.
However, the default location is the /etc/ld.so.conf
file. On modern debian systems that points to the folder /etc/ld.so.conf.d
.
In there you should find several .conf files.
One of those files on an armhf system should be arm-linux-gnueabihf.conf
(so /etc/ld.so.conf.d/arm-linux-gnueabihf.conf
and that one should contain
# Multiarch support
/lib/arm-linux-gnueabihf
/usr/lib/arm-linux-gnueabihf
I assume that one is missing or incomplete on the OSMC systems.
@Harry-van-der-Wolf said in Installing Pimatic 0.9 @OSMC?:
It doesn’t help by exporting something from your own shell.
I have tried this ffrom the command line, i.e.
export PATH=$PATH:/lib/arm-linux-gnueabihf/
export LD_LIBRARY_PATH=/lib/arm-linux-gnueabihf/
./vhduino
/etc/ld.so.conf
I think this the configuration for link loader. I am not sure if this is the right place.
One of those files on an armhf system should be arm-linux-gnueabihf.conf … I assume that one is missing or incomplete on the OSMC systems.
No. I have checked this. The conetnt is basically the same on Raspbian and OSMC. May be the issue is related to https://wiki.debian.org/Multiarch/LibraryPathOverview#ELF_interpreter-1
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Yes,it is the link loader run location.
Maybe I’m wrong but according to the documentation
"/etc/ld.so.conf File containing a list of colon, space, tab, newline, or comma-separated directories in which to search for libraries."
If the content is the same it might indeed be what you mention.
Fixture for OSMC is on its way (only applies to new OSMC installs). For the time being use the work-around by creating the symbolic link as described earlier. sudo ln -s /lib/arm-linux-gnueabihf/ld-linux.so.3 /lib/ld-linux.so.3
https://github.com/osmc/osmc/commit/29154daade0c4539fe24b70faeab6f10788b171d
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Aprt from this we should provide an update build of vhduino to be created with the current toolchain.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
I’m very Thankful Guys!
Muchas Gracias
Greets Dodo
Can I overclock osmc? i read somewhere you shoudn’t overclock a system with pimatic?
@Dodo88 said in Installing Pimatic 0.9 @OSMC?:
Can I overclock osmc? i read somewhere you shoudn’t overclock a system with pimatic?
I am not aware of this. I think overclocking is not specifcally a problem with pimatic but you may run into stability problems with the hardware. Thus, I won’t recommend it, You’ll be better off with an Raspi 3 which cannot be overclocked anyway.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
Okay, thx!
@Dodo88 Some links on the topic:
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
I am locking this topic now
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law