• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
OSMC pilight
#1
Since my debian runs pilight perfectly now. I tried to install pilight onto my osmc.
That didn't work yet...

Here is my /var/log/pilight.log

Code:
[Dec 01 21:14:19:988933] pilight-daemon: INFO: version v7.0
[ Dec 01 21:14:20:94100] pilight-daemon: NOTICE: a pilight daemon was found @192.168.xxx.xxx, clientizing
[Dec 01 21:14:20:164955] pilight-daemon: ERROR: raspberrypi->isr: Failed to set interrupt edge to both
[Dec 01 21:14:20:167467] pilight-daemon: ERROR: raspberrypi: error while calling isr
[Dec 01 21:14:20:175016] pilight-daemon: ERROR: unable to register interrupt for pin 1
[Dec 01 21:38:51:548099] pilight-daemon: INFO: removed stale pid_file /var/run/pilight.pid
[Dec 01 22:00:01:287928] pilight-daemon: INFO: version v7.0
[Dec 01 22:00:01:383995] pilight-daemon: INFO: no pilight daemon found, daemonizing
[Dec 01 22:00:01:385396] pilight-daemon: INFO: daemon listening to port: 32904
[Dec 01 22:00:01:385656] pilight-daemon: ERROR: cannot bind to the ssdp multicast network

searching for the erros I found this:
http://forum.pilight.org/Thread-problem-...ending-pin

There was e.g. suggested to install wiringx

Code:
sudo apt-get install git-core
sudo apt-get install cmake
sudo apt-get install gcc
sudo apt-get install libc-dev

Code:
git clone https://github.com/wiringX/wiringX.git
sudo su
cd wiringX
mkdir build
cd build
cmake ..
make

that failed though with:
Code:
# make
[ 63%] Built target sources
[ 63%] Built target wiringx_shared
Linking C executable wiringx-blink
libwiringX.so: undefined reference to `i2c_smbus_write_byte'
libwiringX.so: undefined reference to `i2c_smbus_read_byte'
libwiringX.so: undefined reference to `i2c_smbus_write_byte_data'
libwiringX.so: undefined reference to `i2c_smbus_write_word_data'
libwiringX.so: undefined reference to `i2c_smbus_read_word_data'
libwiringX.so: undefined reference to `i2c_smbus_read_byte_data'
collect2: error: ld returned 1 exit status
CMakeFiles/wiringx-blink.dir/build.make:84: recipe for target 'wiringx-blink' failed
make[2]: *** [wiringx-blink] Error 1
CMakeFiles/Makefile2:126: recipe for target 'CMakeFiles/wiringx-blink.dir/all' failed
make[1]: *** [CMakeFiles/wiringx-blink.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
make: *** [all] Error 2

Any ideas?
Thank you!
Raspberry Pi Vers. B. - Raspbian GNU/Linux 8.0 - Aukru 433MHz sender and receiver, Mumbi m-FS300 and intertechno 1500
deb http://apt.pilight.org/ nightly main
http://forum.pilight.org/Thread-Mumbi-m-...light-v6-0
support https://fsfe.org/
 
Reply
#2
(Installing wiringx was to test if the hardware works as needed by using the wiringx tests.)
Do you get this error with a fresh clone? This error was just (supposedly) fixed here: https://github.com/wiringX/wiringX/issues/51
 
Reply
#3
Since the changes were made 7 days ago and my trial and error was yesterday, I'd exclude that possible error. Any other idea? Did I forget to install some requirements since pilight and wiringx seem to expect debian and not something like osmc?
Raspberry Pi Vers. B. - Raspbian GNU/Linux 8.0 - Aukru 433MHz sender and receiver, Mumbi m-FS300 and intertechno 1500
deb http://apt.pilight.org/ nightly main
http://forum.pilight.org/Thread-Mumbi-m-...light-v6-0
support https://fsfe.org/
 
Reply
#4
Can you test with the code from before the changes were made 5 days ago? So commit https://github.com/wiringX/wiringX/commi...9cfb53f9c2

Both wiringx and pilight were designed to support many platforms, although it could be that it won't work out of the box on your system… Afaik, it shouldn't really need further dependencies apart from the build tools I think.
 
Reply
#5
I have pilight on OSMC and everything works well.
You just need to add an entry in rc.local
Code:
sleep 10
service pilight restart
exit 0
I do not know why pilight does not start with the system?
 
Reply
#6
I did a wider search now...

"libwiringX.so: undefined reference to `i2c_smbus_write_byte'"
look what I have found...

http://www.forum-raspberrypi.de/Thread-p...r-raspbian

Could that be connected?

Thank you so far...but your ideas didn't help yet. Is there anything else?
Thank you again!

I changed manually
Code:
ls -la /home/user/wiringX/examples/blink.c
-rwxr--r-- 1 user user 1085 Dez  3 13:37 /home/user/wiringX/examples/blink.c
Code:
/home/user/wiringX/examples/blink.c
/home/user/wiringX/examples/interrupt.c
/home/user/wiringX/examples/read.c
/home/user/wiringX/examples/wiringX.c
After that the line with 9% was new, the rest stayed the same.
Code:
# make
Scanning dependencies of target sources
[  9%] Building C object CMakeFiles/sources.dir/src/wiringX.c.o
[ 63%] Built target sources
Linking C shared library libwiringX.so
[ 63%] Built target wiringx_shared
Scanning dependencies of target wiringx-blink
[ 72%] Building C object CMakeFiles/wiringx-blink.dir/examples/blink.c.o
Linking C executable wiringx-blink
libwiringX.so: undefined reference to `i2c_smbus_write_byte'
libwiringX.so: undefined reference to `i2c_smbus_read_byte'
libwiringX.so: undefined reference to `i2c_smbus_write_byte_data'
libwiringX.so: undefined reference to `i2c_smbus_write_word_data'
libwiringX.so: undefined reference to `i2c_smbus_read_word_data'
libwiringX.so: undefined reference to `i2c_smbus_read_byte_data'
collect2: error: ld returned 1 exit status
CMakeFiles/wiringx-blink.dir/build.make:84: recipe for target 'wiringx-blink' failed
make[2]: *** [wiringx-blink] Error 1
CMakeFiles/Makefile2:126: recipe for target 'CMakeFiles/wiringx-blink.dir/all' failed
make[1]: *** [CMakeFiles/wiringx-blink.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
make: *** [all] Error 2
Raspberry Pi Vers. B. - Raspbian GNU/Linux 8.0 - Aukru 433MHz sender and receiver, Mumbi m-FS300 and intertechno 1500
deb http://apt.pilight.org/ nightly main
http://forum.pilight.org/Thread-Mumbi-m-...light-v6-0
support https://fsfe.org/
 
Reply
#7
Try again with the latest commits.
 
Reply
#8
Thank you for reading and staying focussed on my problem! I do appreciate any input.wiringX didn't work out. Installed like this:
Code:
sudo rm -rf /home/user/wiringX
git clone https://github.com/wiringX/wiringX.git
sudo su
cd wiringX
mkdir build
cd build
cmake ..
make

Here are the errors: Any ideas what I might do wrong?
Code:
make &> results.txt
[ 10%] Building C object CMakeFiles/sources.dir/src/radxa.c.o
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:37:8: error: redefinition of ‘struct i2c_msg’
struct i2c_msg {
        ^
In file included from /home/user/wiringX/src/i2c-dev.h:18:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c.h:68:8: note: originally defined here
struct i2c_msg {
        ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:89:7: error: redefinition of ‘union i2c_smbus_data’
union i2c_smbus_data {
       ^
In file included from /home/user/wiringX/src/i2c-dev.h:18:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c.h:128:7: note: originally defined here
union i2c_smbus_data {
       ^
In file included from /home/user/wiringX/src/radxa.c:33:0:
/home/user/wiringX/src/i2c-dev.h:22:14: error: conflicting types for ‘i2c_smbus_access’
INLINE __s32 i2c_smbus_access(int fd, char rw, int cmd, int size, union i2c_smbus_data *data) __attribute__((always_inline));
              ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:156:21: note: previous definition of ‘i2c_smbus_access’ was here
static inline __s32 i2c_smbus_access(int file, char read_write, __u8 command,
                     ^
In file included from /home/user/wiringX/src/radxa.c:33:0:
/home/user/wiringX/src/i2c-dev.h:24:14: error: conflicting types for ‘i2c_smbus_write_byte’
INLINE __s32 i2c_smbus_write_byte(int fd, int value) __attribute__((always_inline));
              ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:183:21: note: previous definition of ‘i2c_smbus_write_byte’ was here
static inline __s32 i2c_smbus_write_byte(int file, __u8 value)
                     ^
In file included from /home/user/wiringX/src/radxa.c:33:0:
/home/user/wiringX/src/i2c-dev.h:25:14: error: conflicting types for ‘i2c_smbus_read_byte_data’
INLINE __s32 i2c_smbus_read_byte_data(int fd, int cmd) __attribute__((always_inline));
              ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:189:21: note: previous definition of ‘i2c_smbus_read_byte_data’ was here
static inline __s32 i2c_smbus_read_byte_data(int file, __u8 command)
                     ^
In file included from /home/user/wiringX/src/radxa.c:33:0:
/home/user/wiringX/src/i2c-dev.h:26:14: error: conflicting types for ‘i2c_smbus_write_byte_data’
INLINE __s32 i2c_smbus_write_byte_data(int fd, int cmd, int value) __attribute__((always_inline));
              ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:199:21: note: previous definition of ‘i2c_smbus_write_byte_data’ was here
static inline __s32 i2c_smbus_write_byte_data(int file, __u8 command,
                     ^
In file included from /home/user/wiringX/src/radxa.c:33:0:
/home/user/wiringX/src/i2c-dev.h:27:14: error: conflicting types for ‘i2c_smbus_read_word_data’
INLINE __s32 i2c_smbus_read_word_data(int fd, int cmd) __attribute__((always_inline));
              ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:208:21: note: previous definition of ‘i2c_smbus_read_word_data’ was here
static inline __s32 i2c_smbus_read_word_data(int file, __u8 command)
                     ^
In file included from /home/user/wiringX/src/radxa.c:33:0:
/home/user/wiringX/src/i2c-dev.h:28:14: error: conflicting types for ‘i2c_smbus_write_word_data’
INLINE __s32 i2c_smbus_write_word_data(int fd, int cmd, __u16 value) __attribute__((always_inline));
              ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:218:21: note: previous definition of ‘i2c_smbus_write_word_data’ was here
static inline __s32 i2c_smbus_write_word_data(int file, __u8 command,
                     ^
In file included from /home/user/wiringX/src/radxa.c:33:0:
/home/user/wiringX/src/i2c-dev.h:40:14: error: redefinition of ‘i2c_smbus_read_byte’
INLINE __s32 i2c_smbus_read_byte(int fd) {
              ^
In file included from /home/user/wiringX/src/i2c-dev.h:19:0,
                 from /home/user/wiringX/src/radxa.c:33:
/usr/include/linux/i2c-dev.h:174:21: note: previous definition of ‘i2c_smbus_read_byte’ was here
static inline __s32 i2c_smbus_read_byte(int file)
                     ^
/home/user/wiringX/src/radxa.c:78:1: warning: useless storage class specifier in empty declaration
};
^
/home/user/wiringX/src/radxa.c:109:1: warning: useless storage class specifier in empty declaration
};
^
/home/user/wiringX/src/radxa.c:122:1: warning: useless storage class specifier in empty declaration
};
^
/home/user/wiringX/src/radxa.c: In function ‘radxaSetup’:
/home/user/wiringX/src/radxa.c:51:25: warning: passing argument 1 of ‘map_reg’ makes pointer from integer without a cast
#define RK30_AIN_BASE   0x2006c000
                         ^
/home/user/wiringX/src/radxa.c:684:16: note: in expansion of macro ‘RK30_AIN_BASE’
  ret = map_reg(RK30_AIN_BASE, &ain);
                ^
/home/user/wiringX/src/radxa.c:243:12: note: expected ‘void *’ but argument is of type ‘int’
static int map_reg(void *reg, void **reg_mapped) {
            ^
/home/user/wiringX/src/radxa.c:684:31: warning: passing argument 2 of ‘map_reg’ from incompatible pointer type
  ret = map_reg(RK30_AIN_BASE, &ain);
                               ^
/home/user/wiringX/src/radxa.c:243:12: note: expected ‘void **’ but argument is of type ‘volatile void **’
static int map_reg(void *reg, void **reg_mapped) {
            ^
CMakeFiles/sources.dir/build.make:53: recipe for target 'CMakeFiles/sources.dir/src/radxa.c.o' failed
make[2]: *** [CMakeFiles/sources.dir/src/radxa.c.o] Error 1
CMakeFiles/Makefile2:60: recipe for target 'CMakeFiles/sources.dir/all' failed
make[1]: *** [CMakeFiles/sources.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
make: *** [all] Error 2

pilight

Code:
$ history
  154  rm -rf pilight
  155  sudo rm -rf /home/user/pilight
  156  git clone --depth 5 -b master https://github.com/pilight/pilight.git
  157  cd pilight
  158  chmod +x setup.sh
  159  sudo ./setup.sh
until here everything seems to have worked just fine.
Now I can't start pilight-daemon out of the box.
Code:
160  sudo pilight-daemon
then I want to know where pilight-daemon is located:
Code:
161  locate pilight-daemon
  162  sudo updatedb
  163  locate pilight-daemon
Code:
$ locate pilight-daemon
/home/user/pilight/build/pilight-daemon
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/C.includecache
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/DependInfo.cmake
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/build.make
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/cmake_clean.cmake
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/daemon.c.o
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/depend.internal
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/depend.make
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/flags.make
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/link.txt
/home/user/pilight/build/CMakeFiles/pilight-daemon.dir/progress.make
Code:
164  sudo /usr/local/sbin/pilight-daemon
while looking with 2 other screen-sessions into
Code:
$ sudo tail -f /var/log/pilight.err
[Dec 05 14:07:41:493162] pilight-daemon: INFO: version v7.0
and
Code:
$ sudo tail -f /var/log/pilight.log
[Dec 05 12:28:39:863196] pilight-daemon: INFO: version v7.0
[Dec 05 12:28:39:964242] pilight-daemon: NOTICE: a pilight daemon was found @192.168.xxx.xxx, clientizing
looks good so far, even though the path to pilight-daemon was not found at once.
Where do I add the path in osmc to /usr/local/sbin/?
Code:
165  sudo service pilight start
HERE IS THE ERROR, I think...
Code:
sudo tail -f /var/log/pilight.log
[ Dec 05 12:28:40:13382] pilight-daemon: ERROR: raspberrypi->isr: Failed to set interrupt edge to both
[ Dec 05 12:28:40:13486] pilight-daemon: ERROR: raspberrypi: error while calling isr
[ Dec 05 12:28:40:46851] pilight-daemon: ERROR: unable to register interrupt for pin 1

Interesting detail:
The error message in pilight.log disappears, if I disconnect the Sintron Raspberry Pi -GPIO Extension board v2.2. cobbler board.

So I am thinking it could be a wiring problem, a hardware problem so to say...

This is what I was trying to copy, it is in german though:
http://raspberry.tips/hausautomatisierun...tisierung/

This is my hardware setup:
Overview
[Image: 23890900vm.jpg]
Details
[Image: 23892502oy.jpg]
Receiver
[Image: 23892484vh.jpg]
Sender
[Image: 23892488xw.jpg]
Raspberry Pi Vers. B. - Raspbian GNU/Linux 8.0 - Aukru 433MHz sender and receiver, Mumbi m-FS300 and intertechno 1500
deb http://apt.pilight.org/ nightly main
http://forum.pilight.org/Thread-Mumbi-m-...light-v6-0
support https://fsfe.org/
 
Reply
#9
wiringX should compile fine. The errors you post don't make sense.
 
Reply
#10
are my installation procedures ok?
Raspberry Pi Vers. B. - Raspbian GNU/Linux 8.0 - Aukru 433MHz sender and receiver, Mumbi m-FS300 and intertechno 1500
deb http://apt.pilight.org/ nightly main
http://forum.pilight.org/Thread-Mumbi-m-...light-v6-0
support https://fsfe.org/
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
Question pilight stopped working sl4m01 3 407 11-26-2020, 09:17 PM
Last Post: PPacman
  pilight-raw changes output format from 7 to 8 Rschnauzer 1 262 11-26-2020, 01:52 PM
Last Post: curlymo
Question pilight nightly webgui offline after some hours fleisch 4 306 10-26-2020, 05:19 PM
Last Post: fleisch
  pilight bugs Ascenion 1 468 03-23-2020, 06:29 PM
Last Post: curlymo
  [Solved] pilight service crashing on first webserver access after reboot VrahoK 20 3,419 12-21-2019, 09:46 AM
Last Post: curlymo
  pilight-control modify values coolinx 16 2,729 11-13-2019, 08:02 PM
Last Post: curlymo
  Bug: double free or corruption in pilight-send blackzombie 12 2,371 10-07-2019, 08:15 PM
Last Post: blackzombie
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 790 08-13-2019, 05:43 PM
Last Post: curlymo
  pilight Nano USB interface curlymo 228 136,570 07-10-2019, 06:14 PM
Last Post: curlymo
  problems compiling pilight on Odroid C2 WitchDoctor 101 24,542 03-14-2019, 09:01 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)