09-03-2017, 02:47 PM
And all pilight versions are the same?
|
Thread Rating:
AdHoc network with 2 Raspberry and 2 GPIO transmitter not working
|
09-03-2017, 02:51 PM
Yes, did a fresh git clone --depth 5 -b development https://github.com/pilight/pilight.git on all three Raspis today.
Werner
Werner
09-03-2017, 04:25 PM
Can you try with the latest commit?
09-03-2017, 04:54 PM
after compiling with the latest commit (fresh clone) pilight does not start:
/var/log/messages:
/etc/init.d/pilight status:
/var/log/messages:
Quote:Sep 3 16:53:46 pilight kernel: [357546.048212] Program pilight-daemon tried to access /dev/mem between 20200000->20201000.
Sep 3 16:53:46 pilight kernel: [357546.055612] pilight-daemon[17609]: segfault at d ip b6e36ffb sp bff9e140 error 4 in liblua5.1.so.0.0.0[b6e2c000+31000]
/etc/init.d/pilight status:
Quote:● pilight.service - LSB: Starts pilight-daemon
Loaded: loaded (/etc/init.d/pilight)
Active: active (exited) since Son 2017-09-03 16:53:46 BST; 3min 39s ago
Process: 17600 ExecStart=/etc/init.d/pilight start (code=exited, status=0/SUCCESS)
Sep 03 16:53:46 pilight systemd[1]: Starting LSB: Starts pilight-daemon...
Sep 03 16:53:46 pilight pilight[17600]: Starting : pilightSegmentation fault
Sep 03 16:53:46 pilight pilight[17600]: failed!
Sep 03 16:53:46 pilight systemd[1]: Started LSB: Starts pilight-daemon.
09-03-2017, 05:30 PM
Do you have the right platform configured?
The master does not have GPIO capability because pilight is installed on a virtualized raspberry pi system (Debian + Pixel for PC & Mac), so which platform should I use for the master?
The slaves are raspberry pi 2 & 3 and have "gpio-platform": "raspberrypi2" resp. "gpio-platform": "raspberrypi3".
OK, used "gpio-platform": "none", works now. Have to compile & test, in a few minutes I report if success or not.
Werner
changes you made do not resolve the issue. Stil having interferences.
Werner
The slaves are raspberry pi 2 & 3 and have "gpio-platform": "raspberrypi2" resp. "gpio-platform": "raspberrypi3".
OK, used "gpio-platform": "none", works now. Have to compile & test, in a few minutes I report if success or not.
Werner
changes you made do not resolve the issue. Stil having interferences.
Werner
09-03-2017, 06:52 PM
Can you actually test if the nodes are sending or not with a LED?
09-03-2017, 07:05 PM
If you tell me how to connect the LED I can test it tomorrow.
Did instead a simple test:
Stopped pilight on one of the two nodes, switching lights on/off works on a device not working with both nodes enabled. Now enabled pilight on this node, disabled on the other node, switching lights on/off works again (tested with two different switches). So for me its clear, uuid config does not work.
Last week I was able to compile rewrite branch on my devices, tested uuid config and was pleased that with both nodes active not interference. But had problems with rules and switched back to development branch.
Werner
Did instead a simple test:
Stopped pilight on one of the two nodes, switching lights on/off works on a device not working with both nodes enabled. Now enabled pilight on this node, disabled on the other node, switching lights on/off works again (tested with two different switches). So for me its clear, uuid config does not work.
Last week I was able to compile rewrite branch on my devices, tested uuid config and was pleased that with both nodes active not interference. But had problems with rules and switched back to development branch.
Werner
09-03-2017, 07:34 PM
What you do is the following:
1. Set UUID for 433.92 devices for one of the nodes.
2. Connect that node and when switching only the matching UUID node should sent.
I will test myself in the upcoming week.
1. Set UUID for 433.92 devices for one of the nodes.
2. Connect that node and when switching only the matching UUID node should sent.
I will test myself in the upcoming week.
Browsing: 1 Guest(s)