• 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
pilight 8.0
#11
First of all libuv doesn't replace pthread in anyway. It still uses it under the hood, but it makes it easier to work on non-blocking io.

Secondly, have you checked my PR in which i tagged you. It contains new code that should fix all these issues.
 
Reply
#12
Question 
Just one question, when is it planned to switch the stable release to 8.0 ?

Thanks
 
Reply
#13
When i'm done with the documentation.
 
Reply
#14
Documentation is done, new stable code base is done. Just waiting for some documentation on the PR developers of the Quigg GT-9000 and the Secudo / FlammEx sensor:

https://github.com/pilight/pilight/pull/239
https://github.com/pilight/pilight/pull/263
 
Reply
#15
Thank you for switching the stable release to 8.0!

Unfortunately it does not seem to work with my RaspberryPi2. I edited config.json and changed to

Code:
...
               "gpio-platform": "raspberrypi2"
...
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 1
                }



But if I start pilight-daemon it won't run but only tells me which GPIO platforms are supported...
What could be wrong?
 
Reply
#16
How are you starting pilight (i.e. what command are you running), and what is the exact output? Please post the output here (in code tags Wink)
 
Reply
#17
Double check if you are using the right config file. I'm using the raspberrypi2 myself and it works perfectly.
 
Reply
#18
Where to download pilight v.8?

Can I install v8 as an upgrade? Do you need to do the installation again?
 
Reply
#19
(10-23-2017, 09:09 PM)pilino1234 Wrote: How are you starting pilight (i.e. what command are you running), and what is the exact output? Please post the output here (in code tags Wink)

Nothing special I think...
Probably there is something wrong with pilight-daemon, because no matter which parameters are used, the output is always the usage stuff like below. Even if I call "sudo pilight-daemon –-version": no version output but "usage...".

Code:
pi@raspberrypi:~ $ cat /etc/pilight/config.json
{
        "devices": { },
        "gui": { },
        "rules": { },
        "settings": {
                "log-level": 6,
                "pid-file": "/var/run/pilight.pid",
                "log-file": "/var/log/pilight.log",
                "webserver-enable": 1,
                "webserver-root": "/usr/local/share/pilight/webgui",
                "webserver-http-port": 5001,
                "webserver-cache": 1,
                "whitelist": "",
                "gpio-platform": "raspberrypi2"
        },
        "hardware": {
                "433gpio": {
                        "sender": 0,
                        "receiver": 1
                }
        },
        "registry": { }
}
pi@raspberrypi:~ $ sudo pilight-daemon –D
Usage: pilight-daemon [options]
         -H --help                      display usage summary
         -V --version                   display version
         -C --config                    config file
         -S --server=x.x.x.x            connect to server address
         -P --port=xxxx                 connect to server port
         -F --foreground                do not daemonize
         -D --debug                     do not daemonize and
                                        show debug information
            --stacktracer               show internal function calls
            --threadprofiler            show per thread cpu usage
            --debuglevel                show additional development info

        The following GPIO platforms are supported:
        - none
        - odroidxu4
        - odroidc2
        - odroidc1
        - raspberrypi3
        - raspberrypi2
        - raspberrypizero
        - raspberrypi1b+
        - raspberrypi1b2
        - raspberrypi1b1
        - hummingboard_edge_dq
        - hummingboard_gate_dq
        - hummingboard_edge_sdl
        - hummingboard_gate_sdl
        - hummingboard_base_dq
        - hummingboard_pro_dq
        - hummingboard_base_sdl
        - hummingboard_pro_sdl
        - orangepipc+
        - bananapim2
        - bananapi1
        - pcduino1

pi@raspberrypi:~ $ pilight-receive
[Oct 24 06:25:45:215963] pilight-receive: NOTICE: no pilight ssdp connections found
pi@raspberrypi:~ $
 
Reply
#20
I can't reproduce your issue with the code from the master branch and your config.



Unrelated bug: When defining a hardware platform such as raspberrypi2 and running this config on a regular computer, pilight (well, wiringx) segfaults. Working on a backtrace, although compiling and installing a Debug build of wiringx doesn't help:

Code:
(gdb) bt full
#0  0x00007ffff67f7ac0 in soc_readl () from /usr/lib/libwiringx.so
No symbol table info available.
#1  0x00007ffff67fc8a8 in broadcom2836PinMode () from /usr/lib/libwiringx.so
No symbol table info available.
#2  0x00007ffff745bdec in gpio433HwInit () at /home/martin/git/pilight/pilight/libs/pilight/hardware/433gpio.c:53
        platform = 0x62cf30 "raspberrypi2"
#3  0x000000000040ad8f in start_pilight (argc=4, argv=0x7fffffffeb78) at /home/martin/git/pilight/pilight/daemon.c:2556
        options = 0x60e510
        ssdp_list = 0x0
        buffer = "11739", '\000' <repeats 1019 times>
        verbosity_changed = 1
        show_default = 0
        show_version = 0
        show_help = 0
        f = 4
        stmp = 0x629dc0 "pilight.log"
        args = 0x0
        p = 0x0
        port = 0
        nrdevs = 1
        x = 0
        devs = 0x0
        tmp_confhw = 0x62cf50
        ntpsync = 0x0
#4  0x000000000040b05b in main (argc=4, argv=0x7fffffffeb78) at /home/martin/git/pilight/pilight/daemon.c:2797
        ret = 0

How to reproduce: Take a working config running on a regular computer (a laptop or whatever), and add an incorrect "gpio-platform" setting, such as "raspberrypi2", then run the pilight daemon with this config. Result: segfault, an error message would be nice though.
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  pilight bugs Ascenion 1 283 03-23-2020, 06:29 PM
Last Post: curlymo
  [Solved] pilight service crashing on first webserver access after reboot VrahoK 20 2,287 12-21-2019, 09:46 AM
Last Post: curlymo
  pilight-control modify values coolinx 16 1,986 11-13-2019, 08:02 PM
Last Post: curlymo
  Bug: double free or corruption in pilight-send blackzombie 12 1,632 10-07-2019, 08:15 PM
Last Post: blackzombie
  [Fixed] High CPU usage when pilight usb nano disconnects DieterK 1 617 08-13-2019, 05:43 PM
Last Post: curlymo
  pilight Nano USB interface curlymo 228 125,432 07-10-2019, 06:14 PM
Last Post: curlymo
  problems compiling pilight on Odroid C2 WitchDoctor 101 20,022 03-14-2019, 09:01 PM
Last Post: curlymo
  pilight 8 what chages for custom protocols? polo 11 4,729 02-15-2019, 06:22 PM
Last Post: polo
  pilight-debug shows nothing minhdomanh 3 1,110 10-18-2018, 07:01 AM
Last Post: felfert
  pilight-send and pilight-daemon DieterK 0 969 06-20-2018, 12:44 AM
Last Post: DieterK

Forum Jump:


Browsing: 1 Guest(s)