• 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
hardware module issues in nightly
#1
Version 8.1.4-31-gef298946 with configured hardware module does not start while leaving the hardware config section empty does not show the error.

Code:
sudo pilight-daemon -S 127.0.0.1 -P 5000 -D
pilight-daemon: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/settings.lua v1.0
pilight-daemon: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/hardware.lua v1.0
pilight-daemon: DEBUG: loaded storage /usr/local/lib/pilight/storage/json/registry.lua v1.0
pilight-daemon: INFO: datetime datetimedev xx.xxxxxx:xx.xxxxxx seems to be in timezone: Europe/Berlin
pilight-daemon: INFO: sunriseset sunrisesetdev xx.xxxxxx:xx.xxxxxx seems to be in timezone: Europe/Berlin
pilight-daemon: DEBUG: loaded event function /usr/local/lib/pilight/functions/min.lua v2.1
pilight-daemon: DEBUG: loaded event function /usr/local/lib/pilight/functions/max.lua v2.1
pilight-daemon: DEBUG: loaded event function /usr/local/lib/pilight/functions/date_format.lua v1.0
pilight-daemon: DEBUG: loaded event function /usr/local/lib/pilight/functions/date_add.lua v2.0
pilight-daemon: DEBUG: loaded event function /usr/local/lib/pilight/functions/random.lua v2.1
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/plus.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/ge.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/minus.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/le.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/or.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/ne.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/divide.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/modulus.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/eq.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/multiply.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/lt.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/and.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/gt.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/intdivide.lua v1.0
pilight-daemon: DEBUG: loaded event operator /usr/local/lib/pilight/operators/concat.lua v1.0
pilight-daemon: DEBUG: loaded event action /usr/local/lib/pilight/actions/sendmail.lua v4.1
pilight-daemon: DEBUG: loaded event action /usr/local/lib/pilight/actions/switch.lua v4.2
pilight-daemon: DEBUG: loaded event action /usr/local/lib/pilight/actions/label.lua v4.1
pilight-daemon: DEBUG: loaded event action /usr/local/lib/pilight/actions/pushbullet.lua v1.0
pilight-daemon: DEBUG: loaded event action /usr/local/lib/pilight/actions/pushover.lua v1.0
pilight-daemon: DEBUG: loaded event action /usr/local/lib/pilight/actions/toggle.lua v4.1
pilight-daemon: DEBUG: loaded event action /usr/local/lib/pilight/actions/dim.lua v4.1
pilight-daemon: INFO: rule #1 group-decolight was parsed in 0.006213 seconds
pilight-daemon: INFO: rule #2 sunrise-decolight was parsed in 0.007898 seconds
pilight-daemon: INFO: rule #3 sunset-decolight was parsed in 0.007991 seconds
pilight-daemon: DEBUG: loaded hardware /usr/local/lib/pilight/hardware/433gpio.lua v4.1
pilight-daemon: DEBUG: loaded hardware /usr/local/lib/pilight/hardware/none.lua v4.1
pilight-daemon: DEBUG: loaded hardware /usr/local/lib/pilight/hardware/433nano.lua v4.1
pilight-daemon: INFO: version v8.1.4-nightly-ef298946
pilight-daemon: NOTICE: pilight daemon not found @127.0.0.1, waiting for it to come online
pilight-daemon: DEBUG: new thread node, 1 thread running
pilight-daemon: DEBUG: new thread sender, 2 threads running
pilight-daemon: DEBUG: new thread broadcaster, 3 threads running
pilight-daemon: ERROR: could not connect to pilight-daemon
pilight-daemon: NOTICE: connection to main pilight daemon lost
pilight-daemon: NOTICE: trying to reconnect...
pilight-daemon: DEBUG: new thread receive parser, 4 threads running
pilight-daemon: DEBUG: broadcasted: {"origin":"receiver","protocol":"sunriseset","message":{"longitude":xx.xxxxxx,"latitude":xx.xxxxxx,"sun":"rise","sunrise":6.22,"sunset":18.12},"uuid":"xxxx-xx-xx-xx-xxxxxx"}
pilight-daemon: DEBUG: lua wiringx on state #0
pilight-daemon: DEBUG: lua wiringx on state #0
pilight-daemon: DEBUG: lua wiringx on state #0
pilight-daemon: DEBUG: broadcasted: {"origin":"receiver","protocol":"datetime","message":{"longitude":xx.xxxxxx,"latitude":xx.xxxxxx,"year":2019,"month":3,"day":15,"weekday":6,"hour":10,"minute":59,"second":43,"dst":0},"uuid":"xxxx-xx-xx-xx-xxxxxx"}
pilight-daemon: DEBUG: cpu: 0.000000%
pilight-daemon: DEBUG: lua wiringx on state #0
pilight-daemon: ERROR: could not connect to pilight-daemon
pilight-daemon: NOTICE: connection to main pilight daemon lost
pilight-daemon: NOTICE: trying to reconnect...
pilight-daemon: DEBUG: lua wiringx on state #0
pilight-daemon: DEBUG: lua wiringx on state #0
pilight-daemon: DEBUG: lua wiringx on state #0
*** Error in `pilight-daemon': double free or corruption (fasttop): 0x01b3d3a0 ***
 
Reply
#2
Can you post a gdb output as described in the manual?
 
Reply
#3
After updating to 8.1.4-31 there is the following problem with the pilight-daemon:



Code:
sudo systemctl status pilight.service -l
[sudo] password for openhabian:
● pilight.service - pilight
   Loaded: loaded (/etc/systemd/system/pilight.service; enabled)
   Active: failed (Result: signal) since Sun 2019-03-17 14:48:22 CET; 2min 44s ago
  Process: 29364 ExecStart=/usr/local/sbin/pilight-daemon (code=exited, status=0/SUCCESS)
 Main PID: 29365 (code=killed, signal=ABRT)

Mar 17 14:48:22 openHABianPi systemd[1]: Started pilight.
Mar 17 14:48:22 openHABianPi pilight-daemon[29364]: *** Error in `/usr/local/sbin/pilight-daemon': double free or corruption (fasttop): 0x019bc340 ***
Mar 17 14:48:22 openHABianPi systemd[1]: pilight.service: main process exited, code=killed, status=6/ABRT
Mar 17 14:48:22 openHABianPi systemd[1]: Unit pilight.service entered failed state.



reinstall, purge and install does not solve the problem. My config.json runs before the update.
System: Raspberry Pi 3 (openhabianpi).
 
Reply
#4
Please post the debug output as said in the previous post.
 
Reply
#5
Yesterday I made the usual systemupdate, including update pilight to

Code:
pilight-daemon version v8.1.4-nightly-525ed5d8

since this pilight starts without any problems the rules are parsed but it doesn't send anymore.
In the log file I find the following informations

Code:
[Mar 21 17:47:10:400153] pilight-daemon: INFO: datetime Tageszeit 16.363449:48.210033 seems to be in timezone: Europe/Bratislava
[Mar 21 17:47:10:409880] pilight-daemon: INFO: sunriseset sunrisesetdev 16.363449:48.210033 seems to be in timezone: Europe/Bratislava
[Mar 21 17:47:10:444693] pilight-daemon: INFO: rule #1 stromaus was parsed in 0.006794 seconds
[Mar 21 17:47:10:450890] pilight-daemon: INFO: rule #2 Handyaus was parsed in 0.006115 seconds
[Mar 21 17:47:10:458651] pilight-daemon: INFO: rule #3 Backoff was parsed in 0.007711 seconds
[Mar 21 17:47:10:462739] pilight-daemon: INFO: rule #4 Orgelan was parsed in 0.004032 seconds
[Mar 21 17:47:10:466663] pilight-daemon: INFO: rule #5 Nachricht was parsed in 0.003866 seconds
[Mar 21 17:47:10:470557] pilight-daemon: INFO: rule #6 Hausalarm was parsed in 0.003843 seconds
[Mar 21 17:47:10:476231] pilight-daemon: INFO: rule #7 Hausalarm2 was parsed in 0.005618 seconds
[Mar 21 17:47:10:480373] pilight-daemon: INFO: rule #8 Hausalarm3 was parsed in 0.004081 seconds
[Mar 21 17:47:10:486231] pilight-daemon: INFO: rule #9 Hausalarm4 was parsed in 0.005796 seconds
[Mar 21 17:47:10:494379] pilight-daemon: INFO: rule #10 Aqua was parsed in 0.008089 seconds
[Mar 21 17:47:10:501312] pilight-daemon: INFO: rule #11 Aqua1 was parsed in 0.006870 seconds
[Mar 21 17:47:10:507850] pilight-daemon: INFO: rule #12 Aqua2 was parsed in 0.006487 seconds
[Mar 21 17:47:10:514149] pilight-daemon: INFO: rule #13 Backup was parsed in 0.006239 seconds
[Mar 21 17:47:10:581217] pilight-daemon: INFO: version v8.1.4-nightly-525ed5d8
[Mar 21 17:47:10:672442] pilight-daemon: INFO: no pilight daemon found, daemonizing
[Mar 21 17:47:10:693471] pilight-daemon: INFO: daemon listening to port: 33739
[Mar 21 17:47:10:699266] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 56548
[Mar 21 17:47:10:712037] pilight-daemon: INFO: secured webserver started on port: 5002 (fd 16)
[Mar 21 17:47:10:712218] pilight-daemon: INFO: regular webserver started on port: 5001 (fd 18)
[Mar 21 17:47:10:803255] pilight-daemon: INFO: new client, ip: 192.168.0.4, port: 34044
[Mar 21 17:47:10:894036] pilight-daemon: NOTICE: 433gpio pulse buffer full
and
[Mar 21 17:48:50:657256] pilight-daemon: NOTICE: 433gpio pulse buffer full
[Mar 21 17:48:50:856962] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:857139] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:857735] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:857875] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:858204] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:858286] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:858558] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:858678] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:858920] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:858990] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:859124] pilight-daemon: ERROR: The Broadcom 2836 GPIO 0 is not set to output mode
[Mar 21 17:48:50:944488] pilight-daemon: NOTICE: 433gpio pulse buffer full

what can I do?

Downgrade to v8.1.4-nightly-d702224c did solve the Problem.
Maybe this will help in Config sender and receiver are otherwise round.

Code:
               "433gpio": {
                       "sender": 1,
                       "receiver": 0
               }
       },
 
Reply
#6
Hi,

I've been trying to get pilight installed and running today. At first, I was following a blog post, but when that wouldn't compile, I started following the installation instructions in the manual. I thought it had worked, but when I got to a test of pilight-send, I encountered the error "no pilight ssdp connections found". I tried a number of things from googling that error. I also tried upgrading to the latest nightly build. When none of that seemed to work, I went back to the install procedure from the blog I'd been following and started resolving dependencies it was complaining about, such as libpcap-dev, libmbedtls-dev, and libluajit. That got pretty far until I hit "fatal error: wiringx.h: No such file or directory". When I googled that, I found a post in this forum admonishing people to follow the manual, so I again tried going through the steps from the manual again and when I eventually tried running pilight-debug (which had been working before), I started seeing this error:

Code:
pilight-debug: NOTICE: 433gpio pulse buffer full

So, out of desperation, I tried just rebooting. I was amazed that when I did, `service pilight status` showed pilight was running! But when I stopped it to try pilight-debug again, I'm still faced with the error:

Code:
pilight-debug: NOTICE: 433gpio pulse buffer full

Google doesn't show this error anywhere. Should I try downgrading?
 
Reply
#7
Please all post the following information:
- Full config?
- Platform?
- 433nano or 433gpio with or without filter?
- What sender / receiver?
 
Reply
#8
Code:
{
    "devices": {
        "Tageszeit": {
            "protocol": ["datetime"],
            "id": [{
                "longitude": 16.363449,
                "latitude": 48.210033
            }],
            "year": 2019,
            "month": 3,
            "day": 27,
            "hour": 5,
            "minute": 26,
            "second": 0,
            "dst": 0,
            "weekday": 4
        },
        "sunrisesetdev": {
            "protocol": ["sunriseset"],
            "id": [{
                "longitude": 16.363449,
                "latitude": 48.210033
            }],
            "sunrise": 5.44,
            "sunset": 18.19,
            "sun": "set"
        },
        "Switch1": {
            "protocol": ["clarus_switch"],
            "id": [{
                "id": "A2",
                "unit": 58
            }],
            "state": "on"
        },
        "Switch2": {
            "protocol": ["clarus_switch"],
            "id": [{
                "id": "B1",
                "unit": 58
            }],
            "state": "off"
        },
        "Switch4": {
            "protocol": ["clarus_switch"],
            "id": [{
                "id": "D3",
                "unit": 58
            }],
            "state": "off"
        },
        "Switch3": {
            "protocol": ["clarus_switch"],
            "id": [{
                "id": "C3",
                "unit": 58
            }],
            "state": "off"
        },
        "Aquarium": {
            "protocol": ["kaku_switch_old"],
            "id": [{
                "id": 2,
                "unit": 2
            }],
            "state": "off"
        },
        "weather": {
            "protocol": ["alecto_wx500"],
            "id": [{
                "id": 233
            }],
            "temperature": 5.9,
            "windavg": 10.00,
            "winddir": 90.00,
            "windgust": 20.00,
            "humidity": 99.0,
            "battery": 0
        },
        "Alarm1": {
            "protocol": ["clarus_switch"],
            "id": [{
                "id": "C15",
                "unit": 59
            }],
            "state": "on"
        },
        "Alarm": {
            "protocol": ["generic_switch"],
            "id": [{
                "id": 100
            }],
            "state": "off"
        }
    },
    "rules": {
        "stromaus": {
            "rule": "IF Tageszeit.second == 0 AND Tageszeit.minute == 50 AND Tageszeit.hour == 19 THEN switch DEVICE Switch3 TO off",
            "active": 1
        },
        "Handyaus": {
            "rule": "IF Tageszeit.second == 0 AND Tageszeit.minute == 0 AND Tageszeit.hour == 10 THEN switch DEVICE Switch1 TO off",
            "active": 1
        },
        "Backoff": {
            "rule": "IF Tageszeit.second == 0 AND Tageszeit.minute == 30 AND Tageszeit.hour == 23 AND Switch2.state == on THEN switch DEVICE Switch2 TO off",
            "active": 1
        },
        "Orgelan": {
            "rule": "IF Switch3.state == on THEN sendmail SUBJECT 'Orgel' MESSAGE 'Orgel ist an' TO xxxx@gmx.de",
            "active": 1
        },
        "Nachricht": {
            "rule": "IF Switch3.state == off THEN sendmail SUBJECT 'Orgel' MESSAGE 'Orgel ist aus' TO xxxx@gmx.de",
            "active": 1
        },
        "Hausalarm": {
            "rule": "IF Alarm.state == on THEN sendmail SUBJECT 'Hausalarm' MESSAGE 'Alarm ist an' TO xxxx@gmx.de",
            "active": 1
        },
        "Hausalarm2": {
            "rule": "IF Alarm1.state == on AND Alarm.state == on THEN sendmail SUBJECT 'Hausalarm' MESSAGE 'Tuer wurde geöffnet' TO xxxx@gmx.de",
            "active": 1
        },
        "Hausalarm3": {
            "rule": "IF Alarm.state == off THEN sendmail SUBJECT 'Hausalarm' MESSAGE 'Alarm wurde ausgeschaltet' TO xxxxx@gmx.de",
            "active": 1
        },
        "Hausalarm4": {
            "rule": "IF Alarm1.state == off AND Alarm.state == on THEN sendmail SUBJECT 'Hausalarm' MESSAGE 'Tuer wurde geöffnet' TO xxx@gmx.de",
            "active": 1
        },
        "Aqua": {
            "rule": "IF (sunrisesetdev.sunset == DATE_FORMAT(Tageszeit, %H.%M)) AND Aquarium.state == off AND Tageszeit.second == 0 THEN switch DEVICE Aquarium TO on",
            "active": 1
        },
        "Aqua1": {
            "rule": "IF sunrisesetdev.sunset == DATE_FORMAT(DATE_ADD(Tageszeit, '+30 MINUTE'), \"%Y-%m-%d %H:%M:%S\", %H.%M) AND Tageszeit.second == 0 THEN switch DEVICE Aquarium TO on",
            "active": 1
        },
        "Aqua2": {
            "rule": "IF Tageszeit.minute == 00 AND Tageszeit.hour == 23 AND Aquarium.state == on  THEN switch DEVICE Aquarium TO off",
            "active": 1
        },
        "Backup": {
            "rule": "IF Tageszeit.weekday == 7 AND Tageszeit.minute == 00 AND Tageszeit.hour == 10 THEN switch DEVICE Switch2 TO on",
            "active": 1
        }
    },
    "gui": {
        "sunrisesetdev": {
            "name": "Sonnen Auf / Untergang",
            "group": ["Allgemein"],
            "media": ["all"]
        },
        "weather": {
            "name": "Außentemperatur",
            "group": ["Allgemein"],
            "media": ["all"],
            "show-wind": 0
        },
        "Tageszeit": {
            "name": "Datum - Uhrzeit",
            "group": ["Allgemein"],
            "media": ["all"],
            "format": "DD-MMM-YYYY HH:mm:ss"
        },
        "Switch1": {
            "name": "Handy Ladestation",
            "group": ["Schreibtisch"],
            "media": ["all"]
        },
        "Switch2": {
            "name": "Backup Laufwerk",
            "group": ["Schreibtisch"],
            "media": ["all"]
        },
        "Switch4": {
            "name": "Wassermann",
            "group": ["Schreibtisch"],
            "media": ["all"]
        },
        "Aquarium": {
            "name": "Wohnzimmer Lampe",
            "group": ["Wohnzimmer"],
            "media": ["all"]
        },
        "Switch3": {
            "name": "Orgel",
            "group": ["Wohnzimmer"],
            "media": ["all"]
        },
        "Alarm": {
            "name": "Türalarm",
            "group": ["Haus"],
            "media": ["all"]
        }
    },
    "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,
        "webgui-websockets": 1,
        "gpio-platform": "raspberrypi2",
        "ntp-servers": ["0.de.pool.ntp.org", "1.de.pool.ntp.org", "2.de.pool.ntp.org"],
        "smtp-sender": "dummy@gmx.net",
        "smtp-host": ".net",
        "smtp-port": 465,
        "smtp-user": "@gmx.net",
        "smtp-password": "xxxx",
        "smtp-ssl": 1
    },
    "hardware": {
        "433gpio": {
            "sender": 1,
            "receiver": 0
        }
    },
    "registry": {
        "webgui": {
            "tabs": 0
        },
        "pilight": {
            "version": {
                "current": "8.1.4"
            }
        },
        "webserver": {
            "ssl": {
                "certificate": {
                    "location": "/etc/pilight/pilight.pem"
                }
            }
        }
    }
}
raspberry 2 b
pilight-daemon version v8.1.4-nightly-d702224c
433 gpio without filter
Receiver RXB6 433MHz Superheterodyne
Sender 433 MHz XY-FST Sender
System Linux Pi2 4.4.50-v7+ #970 SMP Mon Feb 20 19:18:29 GMT 2017 armv7l GNU/Linux
 
Reply
#9
Do you have a filter? If yes, can you check what happens when you use it?
 
Reply
#10
(03-27-2019, 06:29 PM)curlymo Wrote: Do you have a filter? If yes, can you check what happens when you use it?

Sorry no filter
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Strange issues with kaku_switch and v8.1.4 bitboy 7 316 05-13-2019, 09:17 PM
Last Post: curlymo
  Basic testing pilight hardware dirk 5 817 06-07-2018, 06:09 PM
Last Post: curlymo
  Update to v8.0.10-nightly-a1279212 Ulrich.Arnold 3 1,096 06-04-2018, 08:31 PM
Last Post: curlymo
  [Solved] reach of pilight hardware PT-Biker 2 848 05-21-2018, 08:28 AM
Last Post: PT-Biker
  Issues receiving RF OrangeTang 8 838 05-13-2018, 09:27 AM
Last Post: curlymo
  Elro 800 issues after upgrade to 8.0.9 TomiB 2 555 01-29-2018, 10:12 PM
Last Post: TomiB
  Updates for nightly Ulrich.Arnold 1 481 01-26-2018, 07:31 PM
Last Post: curlymo
  pilight works without connected hardware wanky 4 1,350 12-29-2017, 06:10 PM
Last Post: curlymo
  pilight does no longer start because of hardware error stratege-0815 2 924 12-27-2017, 11:16 PM
Last Post: stratege-0815
  Installing WiringX Python Module on Radxa Rock 8BitBob 5 1,207 04-20-2017, 07:20 PM
Last Post: curlymo

Forum Jump:


Browsing: 1 Guest(s)