06-22-2021, 04:43 PM
(This post was last modified: 06-22-2021, 04:44 PM by stanwebber.)
i found this code containing a custom pilight weather protocol on the internet:
github.com/mikepparks/pilight-protocols
i have successfully compiled it in pilight 8.0.2 under raspbian and debian stretch for armhf and aarch64 respectively, but i can't tell if it's working or not. i'm wondering if i missed any steps. here is a rundown of what i did:
- installed libunwind-dev, libwiringx-dev dependencies (aarch64 required me to compile libunwind-1.5.0 from source)
- downloaded and extracted pilight v8.0.2.tar.gz
- cloned github.com/mikepparks/pilight-protocols and copied acurite_606tx.* to pilight_8.0.2/libs/pilight/protocols/433.92/
- ran pilight_8.0.2/setup.sh and unselected all protocols except for cpu_temp, ping and relay (everything not labeled 'protocol_' left selected)
was there something else i needed to do to include the new protocol? pilight appears to run without issues, although i got a segmentation fault on startup with the newest pilight 8.1.5 so i downgraded to a pre-libmbed version which cleared that up.
here is the startup logging in case there's something revealing:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:33:06] INFO: GPIO Platform used: raspberrypi4
[10:33:06] WARNING: SENDER Pin is disabled
[10:33:06] INFO: RECEIVER Pin is: 9
[10:33:07] WARNING: Starting pilight daemon in debug Mode
[Jun 22 15:33:07:856274] pilight-daemon: INFO: version
[Jun 22 15:33:07:857594] pilight-daemon: DEBUG: ssdp sent search
[Jun 22 15:33:07:961895] pilight-daemon: INFO: no pilight daemon found, daemonizing
[Jun 22 15:33:07:963238] pilight-daemon: INFO: daemon listening to port: 5000
[Jun 22 15:33:07:965929] pilight-daemon: DEBUG: new thread socket, 1 thread running
[Jun 22 15:33:07:966293] pilight-daemon: DEBUG: new thread ssdp, 2 threads running
[Jun 22 15:33:07:966604] pilight-daemon: DEBUG: new thread sender, 3 threads running
[Jun 22 15:33:07:966921] pilight-daemon: DEBUG: new thread broadcaster, 4 threads running
[Jun 22 15:33:07:967495] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 38946
[Jun 22 15:33:07:967566] pilight-daemon: DEBUG: client fd: 8
[Jun 22 15:33:07:967614] pilight-daemon: DEBUG: client id: 1
[Jun 22 15:33:07:991928] pilight-daemon: DEBUG: new thread 433gpio, 5 threads running
[Jun 22 15:33:07:992297] pilight-daemon: DEBUG: new thread receive parser, 6 threads running
[Jun 22 15:33:07:993731] pilight-daemon: DEBUG: new thread events client, 7 threads running
[Jun 22 15:33:07:994151] pilight-daemon: DEBUG: new thread events loop, 8 threads running
[Jun 22 15:33:07:994510] pilight-daemon: DEBUG: webserver listening to port 5001
[Jun 22 15:33:07:995606] pilight-daemon: DEBUG: new thread webserver worker #0, 9 threads running
[Jun 22 15:33:07:995974] pilight-daemon: DEBUG: ssdp sent notify
[Jun 22 15:33:07:996562] pilight-daemon: DEBUG: new thread webserver client, 10 threads running
[Jun 22 15:33:07:997058] pilight-daemon: DEBUG: new thread webserver broadcast, 11 threads running
[Jun 22 15:33:07:998000] pilight-daemon: DEBUG: cpu: 0.000000%, ram: 0.146211%
[Jun 22 15:33:07:998666] pilight-daemon: DEBUG: ssdp sent search
[ Jun 22 15:33:08:125] pilight-daemon: DEBUG: ssdp sent notify
[ Jun 22 15:33:08:1153] pilight-daemon: DEBUG: ssdp sent search
[Jun 22 15:33:08:102581] pilight-daemon: INFO: new client, ip: 172.30.33.1, port: 37064
[Jun 22 15:33:08:102886] pilight-daemon: DEBUG: client fd: 14
[Jun 22 15:33:08:103071] pilight-daemon: DEBUG: client id: 2
[Jun 22 15:33:08:102744] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"core":1},"media":"web"}
[Jun 22 15:33:08:102744] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}
[Jun 22 15:33:08:104234] pilight-daemon: INFO: new client, ip: 172.30.33.1, port: 37066
[Jun 22 15:33:08:296937] pilight-daemon: DEBUG: client fd: 16
[Jun 22 15:33:08:297288] pilight-daemon: DEBUG: client id: 3
[Jun 22 15:33:08:297569] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1,"core":1},"media":"web"}
[Jun 22 15:33:08:298203] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}
[Jun 22 15:33:08:298396] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}
[Jun 22 15:33:08:298644] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}
[ Jun 22 15:33:11:1391] pilight-daemon: DEBUG: cpu: 0.090947%, ram: 0.146211%
[ Jun 22 15:33:11:2069] pilight-daemon: DEBUG: socket write succeeded: {"values":{"cpu":0.0909468159968284,"ram":0.1462108774976811},"origin":"core","type":-1,"uuid":"0000-02-42-ac-1e2101"}
[ Jun 22 15:33:11:2131] pilight-daemon: DEBUG: broadcasted: {"values":{"cpu":0.0909468159968284,"ram":0.1462108774976811},"origin":"core","type":-1,"uuid":"0000-02-42-ac-1e2101"}
github.com/mikepparks/pilight-protocols
i have successfully compiled it in pilight 8.0.2 under raspbian and debian stretch for armhf and aarch64 respectively, but i can't tell if it's working or not. i'm wondering if i missed any steps. here is a rundown of what i did:
- installed libunwind-dev, libwiringx-dev dependencies (aarch64 required me to compile libunwind-1.5.0 from source)
- downloaded and extracted pilight v8.0.2.tar.gz
- cloned github.com/mikepparks/pilight-protocols and copied acurite_606tx.* to pilight_8.0.2/libs/pilight/protocols/433.92/
- ran pilight_8.0.2/setup.sh and unselected all protocols except for cpu_temp, ping and relay (everything not labeled 'protocol_' left selected)
was there something else i needed to do to include the new protocol? pilight appears to run without issues, although i got a segmentation fault on startup with the newest pilight 8.1.5 so i downgraded to a pre-libmbed version which cleared that up.
here is the startup logging in case there's something revealing:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[10:33:06] INFO: GPIO Platform used: raspberrypi4
[10:33:06] WARNING: SENDER Pin is disabled
[10:33:06] INFO: RECEIVER Pin is: 9
[10:33:07] WARNING: Starting pilight daemon in debug Mode
[Jun 22 15:33:07:856274] pilight-daemon: INFO: version
[Jun 22 15:33:07:857594] pilight-daemon: DEBUG: ssdp sent search
[Jun 22 15:33:07:961895] pilight-daemon: INFO: no pilight daemon found, daemonizing
[Jun 22 15:33:07:963238] pilight-daemon: INFO: daemon listening to port: 5000
[Jun 22 15:33:07:965929] pilight-daemon: DEBUG: new thread socket, 1 thread running
[Jun 22 15:33:07:966293] pilight-daemon: DEBUG: new thread ssdp, 2 threads running
[Jun 22 15:33:07:966604] pilight-daemon: DEBUG: new thread sender, 3 threads running
[Jun 22 15:33:07:966921] pilight-daemon: DEBUG: new thread broadcaster, 4 threads running
[Jun 22 15:33:07:967495] pilight-daemon: INFO: new client, ip: 127.0.0.1, port: 38946
[Jun 22 15:33:07:967566] pilight-daemon: DEBUG: client fd: 8
[Jun 22 15:33:07:967614] pilight-daemon: DEBUG: client id: 1
[Jun 22 15:33:07:991928] pilight-daemon: DEBUG: new thread 433gpio, 5 threads running
[Jun 22 15:33:07:992297] pilight-daemon: DEBUG: new thread receive parser, 6 threads running
[Jun 22 15:33:07:993731] pilight-daemon: DEBUG: new thread events client, 7 threads running
[Jun 22 15:33:07:994151] pilight-daemon: DEBUG: new thread events loop, 8 threads running
[Jun 22 15:33:07:994510] pilight-daemon: DEBUG: webserver listening to port 5001
[Jun 22 15:33:07:995606] pilight-daemon: DEBUG: new thread webserver worker #0, 9 threads running
[Jun 22 15:33:07:995974] pilight-daemon: DEBUG: ssdp sent notify
[Jun 22 15:33:07:996562] pilight-daemon: DEBUG: new thread webserver client, 10 threads running
[Jun 22 15:33:07:997058] pilight-daemon: DEBUG: new thread webserver broadcast, 11 threads running
[Jun 22 15:33:07:998000] pilight-daemon: DEBUG: cpu: 0.000000%, ram: 0.146211%
[Jun 22 15:33:07:998666] pilight-daemon: DEBUG: ssdp sent search
[ Jun 22 15:33:08:125] pilight-daemon: DEBUG: ssdp sent notify
[ Jun 22 15:33:08:1153] pilight-daemon: DEBUG: ssdp sent search
[Jun 22 15:33:08:102581] pilight-daemon: INFO: new client, ip: 172.30.33.1, port: 37064
[Jun 22 15:33:08:102886] pilight-daemon: DEBUG: client fd: 14
[Jun 22 15:33:08:103071] pilight-daemon: DEBUG: client id: 2
[Jun 22 15:33:08:102744] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"core":1},"media":"web"}
[Jun 22 15:33:08:102744] pilight-daemon: DEBUG: socket write succeeded: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}
[Jun 22 15:33:08:104234] pilight-daemon: INFO: new client, ip: 172.30.33.1, port: 37066
[Jun 22 15:33:08:296937] pilight-daemon: DEBUG: client fd: 16
[Jun 22 15:33:08:297288] pilight-daemon: DEBUG: client id: 3
[Jun 22 15:33:08:297569] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1,"core":1},"media":"web"}
[Jun 22 15:33:08:298203] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}
[Jun 22 15:33:08:298396] pilight-daemon: DEBUG: socket recv: {"action":"identify","options":{"config":1,"receiver":1},"media":"all"}
[Jun 22 15:33:08:298644] pilight-daemon: DEBUG: socket write succeeded: {"status":"success"}
[ Jun 22 15:33:11:1391] pilight-daemon: DEBUG: cpu: 0.090947%, ram: 0.146211%
[ Jun 22 15:33:11:2069] pilight-daemon: DEBUG: socket write succeeded: {"values":{"cpu":0.0909468159968284,"ram":0.1462108774976811},"origin":"core","type":-1,"uuid":"0000-02-42-ac-1e2101"}
[ Jun 22 15:33:11:2131] pilight-daemon: DEBUG: broadcasted: {"values":{"cpu":0.0909468159968284,"ram":0.1462108774976811},"origin":"core","type":-1,"uuid":"0000-02-42-ac-1e2101"}