Error: Lets wait for new config files

Posted on
Sun Apr 09, 2017 12:52 pm
Hackencrash offline
User avatar
Posts: 169
Joined: Dec 16, 2015
Location: UK

Error: Lets wait for new config files

I rebuilt one of my rPi's today after having a corrupt /etc/rsyslog.conf file which may have been like that for some time.

I downloaded the SSD image following your instructions and changed the region, expanded to fill 16GB, set the password as it was before, etc. and all that, however I get the following message over and over again:
Code: Select all
Master not configured yet, lets wait for new config files

I have a static IP entry for this rPi so my DHCP server gave it the same IP as before.

I tried the "initial BASIC setup of rPi servers" option, but this returned "Communication with the plugin timed out." In fact it gives me this message on all of my rPi's, including the working ones.

I tried the various options of sending Config files, rebooting, etc. and even did the "sudo python installLibs.py --force". Incidentally this should read: sudo python ~/pibeacon/installLibs.py --force as you no longer install piBeacon into the home directory.

I am reasonably confident I can get this going either by deleting the original rPi device and creating a new one or by by filling in the values in the ~/pibeacon/parameters file, but was a little taken aback when finding myself in a position of having to reach for a bash editor where none of the billion other options you so splendidly provide do not work.

piBeacon is my favourite plugin :)

Edit: Yep, editing the ~/pibeacon/parameters file worked as expected, yet the "initial BASIC setup of rPi servers" option still fails against this now working rPi with "Communication with the plugin timed out."

Posted on
Sun Apr 09, 2017 1:47 pm
kw123 offline
User avatar
Posts: 5929
Joined: May 12, 2013
Location: Dallas, TX

Re: Error: Lets wait for new config files

could we do an online session? there might a situation were the RPI times out and then reboots before the plugin can load the new files onto the RPI.

Posted on
Sun Apr 09, 2017 2:25 pm
kw123 offline
User avatar
Posts: 5929
Joined: May 12, 2013
Location: Dallas, TX

Re: Error: Lets wait for new config files

And. !!!!! The new OS X does not allow any changes to the hosts file from within the plugin. Some security changes.
If you changed ip or mac you need to manually edit the hosts file and remove the line(s) for these rpi.

Karl


Sent from my iPhone using Tapatalk

Posted on
Sun Apr 09, 2017 3:36 pm
Hackencrash offline
User avatar
Posts: 169
Joined: Dec 16, 2015
Location: UK

Error: Lets wait for new config files

I haven't changed any IP addresses of anything or anything, just rebuilt a rPi from the latest ssd image posted. I did notice when I tried to SSH onto my rPi that, although the rPi had the same IP and MAC address as before, it had a new host ID post rebuild so it wouldn't connect from the Mac server until I manually deleted the entry from the hidden ~/.ssh directory on the Mac. Are you using ssh to connect from plugin to rPi?


Sent from my iPhone using Tapatalk

Posted on
Sun Apr 09, 2017 4:37 pm
kw123 offline
User avatar
Posts: 5929
Joined: May 12, 2013
Location: Dallas, TX

Re: Error: Lets wait for new config files

yes the plugin uses ssh to send files and direct socket to socket for commands.
and yes when you use a new SSD the old certificate are invalid.
and the new feature in OS X does not allow - or at least I have not figured out how to (*)- to change the hosts file from the plugin.. easiest is to delete the hosts file. the plugin can handle the "yes" when asked if you want to ...
the script I was using:
Code: Select all
/usr/bin/perl -pi -e 's/\Q$_// if ($. == " + fix3[1] + ");' " + fix3[0]
.. fix is the output from the ssh file. That worked before, but not since the last OS X upgrade.

you should see something in the log file:
ERROR can not update hosts known_hosts file, "/usr/bin/csrutil status" shows system enabled SIP; please edit manually with
sudo nano ..... .ssh/known_hosts"
and delete line starting with ipnumber"
..
thats explains that ..

with:
Code: Select all
/usr/bin/csrutil status
in a terminal you can check if your csr is set to secure .

Karl

(*) I could pipe the mac password in to the command, but you should have some fun too editing these things ..

Posted on
Mon Apr 10, 2017 2:20 am
Hackencrash offline
User avatar
Posts: 169
Joined: Dec 16, 2015
Location: UK

Error: Lets wait for new config files

Thanks Karl, that explains absolutely everything :idea:

I noticed in my ~/.ssh/known_hosts file that the entries for the other rPi's were wrong as the other rPi's I had renamed and now when I do the initial BASIC setup of rPi servers they all work after I deleted these bad entries from the known_hosts file. It all makes sense now.

I have tried this method before to pipe a password into sudo from within a script to gain elevated rights:
Code: Select all
echo {password} | sudo -S {command}

However, I have had only limited success with this so perhaps this method was one of those blocked in the latest OSX release?

Posted on
Mon Apr 10, 2017 9:50 am
kw123 offline
User avatar
Posts: 5929
Joined: May 12, 2013
Location: Dallas, TX

Re: Error: Lets wait for new config files

I know how to echo the password. But it is getting really difficult to mange all the possibilities. Instead I am now printing a statement in the logfile that tells you what to do.


Sent from my iPhone using Tapatalk

Posted on
Fri Jun 01, 2018 12:49 am
shrxman offline
Posts: 46
Joined: Apr 22, 2015

Re: Error: Lets wait for new config files

Hey Karl,

Sorry if this message seems a little confusing. I have 7 rPi's up and running for a while now, and all has been going well. However, I'm rebuilding an rPi, using the same IP address and hostname, and am getting the same timeout error.. Figured I'd dump all the oddities in here and see if we can sort this out together, but we can work this in whatever way may work for you.

Here's what's in the indigo log after I tried to add the pi back to the system.:
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiAction
Error (client) received unexpected packet response UiAction (waiting for GetUiDynamicList)

and here's what's in piBeacon.log:
23:14:09 -pi= 2
23:14:09 -valuesDict= UiValuesDict : (dict)
MSG : Pi server configuration set (string)
beaconOrSensor : iBeacon and Sensor rPi (string)
confirmPiServer : (string)
confirmPiServerConfig : (string)
enablePiEntries : false (bool)
enableRebootCheck : restartLoop,- (string)
infoLabel11 : (string)
ipNumberPi : 10.10.10.102 (string)
passwordPi : pibeacon (string)
piOnOff : 1 (string)
piServerNumber : 2 (string)
userIdPi : pi (string)
23:14:09 -RPI= {u'piDevId': 860592566, u'userIdPi': u'pi', u'lastMessage': 1527789955.979258, u'passwordPi': u'pibeacon', u'piMAC': u'B8:27:EB:A2:03:A9', u'ipNumberPiSendTo': u'10.10.10.102', u'sendToIndigoSecs': 90, u'emptyMessages': 0, u'piUpToDate': [], u'piNumberReceived': u'2', u'input': {}, u'sensorRefreshSecs': 20, u'enableRebootCheck': u'restartLoop,-', u'deltaTime1': 100, u'piOnOff': u'1', u'deltaTime2': 0.5627121925354004, u'rssiOffset': 0, u'sensorList': '', u'ipNumberPi': u'10.10.10.102', u'output': {}, u'enableiBeacons': u'1', u'deltaChangedSensor': 5}
23:14:09 -fixConfig called from buttonConfirmPiServerConfigCALLBACK; with:['all', 'rpi']

Then the log stops updating anything regarding that rPi and goes on to logging other activities, like a new beacon discovered on some other device.

I'm seeing these errors for virtually all of my pi's, though I know that both the known hosts and the passwords are as expected. I even tried removing my authorized_keys file to see if there was something in there causing issues, but that had no impact.:
spawn sftp -o ConnectTimeout=15 pi@10.10.10.102
pi@10.10.10.102's password:
Permission denied, please try again.
pi@10.10.10.102's password:
23:01:13 -setup pi response (2) error

Here's the output of piBeacon.log when I try to send an ls command to that rPi:
23:28:02 -send YOUR command to rpi 10.10.10.102; "[{\"cmdLine\": \"ls\", \"command\": \"general\"}]"
23:28:02 -error in socket-send to rPi:10.10.10.102 [{"cmdLine": "ls", "command": "general"}]
23:28:02 -line:6053; err:[Errno 61] Connection refused

Incidentally, I don't even see any entry in /var/log/auth.log on the raspberry pi, so I don't think it ever actually tries to ssh to the rPi.

As for the timeout errors, I'm getting them even when i try to update the logging level. I vaguely recall you mentioning in one of these support threads a while back that the tracking for expired/ignored beacons can sometimes cause timeouts if there are too many, and that we should trim/delete that list and just let it rebuild over time. I'm not sure if that's even relevant now, with all of your updates and, if so, where/how to do so anymore. lol

I just tried to disable and enable this new pi in Initial BASIC setup options, got the timeout, but when I reloaded, the action appeared to have succeeded. But again, I see this in the Indigo logs:
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiAction
Error (client) received unexpected packet response UiAction (waiting for GetUiDynamicList)
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiAction
Error (client) received unexpected packet response UiAction (waiting for GetUiDynamicList)


So, I think all of these issues are loosely related, but I just haven't figured out the connection just yet, but these timeouts seem pretty suspicious. ;-)
Any thoughts on where to start with this one?

thanx in advance, as always :-)
~ken

Posted on
Fri Jun 01, 2018 11:00 am
kw123 offline
User avatar
Posts: 5929
Joined: May 12, 2013
Location: Dallas, TX

Error: Lets wait for new config files

Dumb questions:
1. What is the password on the rpi and how did you set it?
2. Nano hosts file on your mac and delete the line of the old rpi

3 which version are you running?

4. You need to enable ssh on the rpi if you have build the ssd yourself: sudo raspi-config
And you need to change local.rc — see how to make an ssd ... for what to do

The latest versions makes it very easy to replace an rpi. Should be 99% automatic if the plugin can ssh to the rpi.

Karl


Sent from my iPhone using Tapatalk

Posted on
Fri Jun 01, 2018 5:28 pm
shrxman offline
Posts: 46
Joined: Apr 22, 2015

Re: Error: Lets wait for new config files

Hey Karl,
No such thing as a dumb question from you., unless it's in response to one of my silly mistakes :-)

1. password is pibeacon, as it's from your stretch image [ 2017-11-29-raspbian-stretch.img ]
2. no entry in /etc/hosts for any of my Pi's. Should there be?
3. pibeacon version = 7.83.217
4. ssh is working fine.. i can get in via password, or using an ssh key so authentication is working fine there.

i think the key issue is the connection refused bit. I do get updates on beacons from the pi's, so some connectivity is functioning just fine.



16:15:55 -creating new beacon, received from pi # 1/B8:27:EB:E1:4E:57: beacon-7E:58:B3:F8:65:71 UUID: 011a0aff4c001005-2576-57503
16:16:12 -RPI# 2 check , too many empty messages in a row: 2
16:16:12 -sending reboot command to RPI
16:16:42 -creating new beacon, received from pi # 1/B8:27:EB:E1:4E:57: beacon-46:8C:35:F9:1B:5A UUID: 00b226f5593b7650bf884f5c844f1005-2832-58974
16:17:38 -RPI# 2 check , too many empty messages in a row: 2
16:17:38 -sending reboot command to RPI
16:18:03 -regular reboot of rpi 10.10.10.102; "[{\"cmdLine\": \"sudo reboot &\", \"command\": \"general\"}]"
16:18:03 -error in socket-send to rPi:10.10.10.102 [{"cmdLine": "sudo reboot &", "command": "general"}]
16:18:03 -line:6053; err:[Errno 61] Connection refused
16:18:19 -hard reboot of rpi 10.10.10.102; "[{\"cmdLine\": \"sync;sleep 2 ;sudo reboot -f &\", \"command\": \"general\"}]"
16:18:19 -error in socket-send to rPi:10.10.10.102 [{"cmdLine": "sync;sleep 2 ;sudo reboot -f &", "command": "general"}]
16:18:19 -line:6053; err:[Errno 61] Connection refused

Posted on
Fri Jun 01, 2018 5:55 pm
kw123 offline
User avatar
Posts: 5929
Joined: May 12, 2013
Location: Dallas, TX

Re: Error: Lets wait for new config files

-" error in socket-send .. connection refused" means the receiver is not running on the RPi

could you ssh to the rpi
ps -ef | grep python

post whats running, should look like:
Code: Select all
root      4616     1  1 18:31 ?        00:00:11 /usr/bin/python /home/pi/pibeacon/simplei2csensors.py
pi        8049 28063  0 18:48 pts/0    00:00:00 grep --color=auto python
root     14882     1  0 08:39 ?        00:04:05 /usr/bin/python /home/pi/pibeacon/master.py
root     15168     1  0 08:39 ?        00:00:51 /usr/bin/python /home/pi/pibeacon/copyToTemp.py
root     15242     1  1 08:39 ?        00:06:25 /usr/bin/python /home/pi/pibeacon/Wire18B20.py
root     15287     1  0 08:39 ?        00:00:28 /usr/bin/python /home/pi/pibeacon/receiveGPIOcommands.py 9999
root     15333     1  8 08:39 ?        00:54:32 /usr/bin/python /home/pi/pibeacon/beaconloop.py

if receiveGPIOcommands.py 9999 is not running ("...connection refused") it does not receive any socket communication from the mac

If master is not running could you start it with
cd pibeacon
sudo python master.py

AND PLEASE DO NOT use ssh key The ssh commands expect a password prompt !!

could you switch on debug "update RPI" in the plugin and post the logfile entries
then do a push of all cgms.. to the new RPI

Karl
also there is a new version, but that is for tomorrow .

Posted on
Sat Jun 02, 2018 11:04 am
shrxman offline
Posts: 46
Joined: Apr 22, 2015

Re: Error: Lets wait for new config files

Ah.. so you're running expect, I see. So that could make a lot of since, though expect usually generates a bit more verbose errors. lol i've removed all keys for the pi user.. Will remove the pi keys on all of my pi's now. will just use another user for my key-based scripts. lol

processes look good:
root 667 1 2 09:49 ? 00:00:00 /usr/bin/python /home/pi/pibeacon/master.py
root 976 1 1 09:49 ? 00:00:00 /usr/bin/python /home/pi/pibeacon/receiveGPIOcommands.py 9999
root 1025 1 1 09:49 ? 00:00:00 /usr/bin/python /home/pi/pibeacon/beaconloop.py

went to update logging and got that 'Communications with the Plugin timed out' error, but from the indigo logs it looks like it took, and when I went back into the configure mode, it does show as being active. I wonder if those timeouts are part of the issue, or are they more common than that?

Jun 2, 2018, 9:51:59 AM
piBeacon logfile handling to : /Users/shrxman/indigo/piBeacon/piBeacon.log
piBeacon myLogSet settting parameters -- logFileActive= user; logFile= /Users/shrxman/indigo/piBeacon/piBeacon.log; debugLevel= [u'UpdateRPI']; maxFileSize= 30000000
Schedule SetVar_Bus_ETA
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiValidate

Jun 2, 2018, 9:52:58 AM
piBeacon logfile handling to : /Users/shrxman/indigo/piBeacon/piBeacon.log
piBeacon myLogSet settting parameters -- logFileActive= user; logFile= /Users/shrxman/indigo/piBeacon/piBeacon.log; debugLevel= [u'UpdateRPI']; maxFileSize= 30000000
Error (client) timeout waiting for plugin response from com.karlwachs.piBeacon for request UiValidate
Error (client) received unexpected packet response UiValidate (waiting for UiClosed1)


after removing the keys, though, things look a lot more promising:
09:59:32 -send Config Files and restart master.py 2 action string:[u'updateParams']
09:59:54 -creating new beacon, received from pi # 1/B8:27:EB:E1:4E:57: beacon-48:5A:59:4A:26:EF UUID: 011a0aff4c001005-2832-40615
09:59:54 -fixConfig in Line '2029' has error='dictionary changed size during iteration'
10:00:10 -updating pi server files
10:00:10 -enter sendFilesToPiServerFTP #2 fileToSend:updateParams.exp
10:00:10 -updating pi server config for # 2
10:00:11 - sbin/ping -c 4 -W 1 -o 10.10.10.102 return-code: 0
10:00:11 -updating pi server config for # 2 executing
/usr/bin/expect '/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/piBeacon.indigoPlugin/Contents/Server Plugin/updateParams.exp' pi pibeacon 10.10.10.102 2 /Users/shrxman/indigo/piBeacon/ '/Library/Application Support/Perceptive Automation/Indigo 7/Plugins/piBeacon.indigoPlugin/Contents/Server Plugin/pi' 15
10:00:23 -setup Pi ok:
spawn sftp -o ConnectTimeout=15 pi@10.10.10.102
pi@10.10.10.102's password:
Connected to 10.10.10.102.
sftp> cd /home/pi/pibeacon
sftp> lcd '/Users/shrxman/indigo/piBeacon///interfaceFiles'
sftp> put 'parameters.2' /home/pi/pibeacon/parameters
Uploading parameters.2 to /home/pi/pibeacon/parameters
parameters.2 100% 1315 21.2KB/s 00:00
sftp> lcd '/Users/shrxman/indigo/piBeacon///rejected'
sftp> get /home/pi/pibeacon/temp/rejects 'rejects.2'
File "/home/pi/pibeacon/temp/rejects" not found.
sftp> rm /home/pi/pibeacon/temp/rejec*
Removing /home/pi/pibeacon/temp/rejec*
Couldn't delete file: No such file or directory
sftp> lcd '/Users/shrxman/indigo/piBeacon///all'
sftp> put * /home/pi/pibeacon/
Uploading beacon_parameters to /home/pi/pibeacon/beacon_parameters
beacon_parameters 100% 1747KB 172.0KB/s 00:10
Uploading touchFile to /home/pi/pibeacon/touchFile
touchFile 100% 13 0.4KB/s 00:00
sftp> put touchFile /home/pi/pibeacon/temp/
Uploading touchFile to /home/pi/pibeacon/temp/touchFile
touchFile 100% 13 0.3KB/s 00:00
sftp> quit

....
0.4KB/s 00:00
sftp> put touchFile /home/pi/pibeacon/temp/
Uploading touchFile to /home/pi/pibeacon/temp/touchFile
touchFile 100% 13 0.3KB/s 00:00
sftp> quit

however, I see this a bit later in the Indigo Log:
10:01:25 -RPI# 2 check , too many empty messages in a row: 2
10:01:25 -sending reboot command to RPI


Getting closer... :-)

Posted on
Sat Jun 02, 2018 11:06 am
shrxman offline
Posts: 46
Joined: Apr 22, 2015

Re: Error: Lets wait for new config files

oops. hit send too soon. I do see this in the permanent.log on the new rPi:
20170909-11:33:27 master rebooting / shutdown reboot now reboot at 2017-09-09 11:33:27.724889 change_in_ramdisk_for_logfiles
20180601-15:09:39 beaconloop in Line '272' has error='(1, 'Operation not permitted')'
20180601-13:44:12 master rebooting / shutdown reboot now reboot at 2018-06-01 13:44:12.078911 change_in_ramdisk_for_logfiles

Posted on
Sat Jun 02, 2018 11:11 am
kw123 offline
User avatar
Posts: 5929
Joined: May 12, 2013
Location: Dallas, TX

Re: Error: Lets wait for new config files

seems like teh auth key was THE issue.

now to the empty messages, please push ALL programs file oct to the new RPI

please ssh two the rpi
cd pibecon
tail -F temp/messageSend
should produce something like this:
Code: Select all
tail -F temp/messageSend
Wire18B20:  {"pi":"3","sensors":{"Wire18B20":{"1330343243":{"temp":[{"28-021565969bff":"22.5"}]}}},"program":"Wire18B20","ipAddress":"192.168.1.23","ts":{"tz":"CDT","time":1527959259.312669}}
tail: temp/messageSend: file truncated
simplei2csensors:  {"pi":"3","sensors":{"i2cTSL2561":{"47929833":{"lux":352.32,"IR":3905.0,"ambient":15428.0}}},"program":"simplei2csensors","ipAddress":"192.168.1.23","ts":{"tz":"CDT","time":1527959262.614139}}
tail: temp/messageSend: file truncated
beaconloop:  {"msgs":[["B8:27:EB:20:90:32",1,"2f234454cf6d4a0fadf2f4911ba9ffa6-9-8",-94.5,-59.0,2,"",30],["00:EA:23:09:81:57",1,"07775dd0111b11e491910800200c9a66-8969-33111",-78.2,-49.0,13,"",30],["00:EA:23:09:81:54",1,"07775dd0111b11e491910800200c9a66-8969-33108",-83.1,-60.0,14,"",30],["00:EA:23:0B:E2:57",1,"07775dd0111b11e491910800200c9a66-8971-57943",-77.8,-49.0,13,"",30],["B8:27:EB:9F:FE:6D",1,"2f234454cf6d4a0fadf2f4911ba9ffa6-9-0",-90.8,-59.0,4,"",30],["B8:27:EB:12:5A:C1",1,"2f234454cf6d4a0fadf2f4911ba9ffa6-9-16",-63.5,-59.0,6,"",30],["5C:F3:70:6D:D9:6E",1,"2f234454cf6d4a0fadf2f4911ba9ffa6-9-7",-85.3,-59.0,9,"",30]],"reason":1,"secsCol":60,"mac":"5C:F3:70:77:FB:6C","program":"beaconloop","ts":{"tz":"CDT","time":1527959275.206882},"pi":"3","ipAddress":"192.168.1.23"}
tail: temp/messageSend: file truncated
Wire18B20:  {"pi":"3","sensors":{"Wire18B20":{"1330343243":{"temp":[{"28-021565969bff":"22.62"}]}}},"program":"Wire18B20","ipAddress":"192.168.1.23","ts":{"tz":"CDT","time":1527959280.988017}}
tail: temp/messageSend: file truncated
simplei2csensors:  {"pi":"3","sensors":{"i2cTSL2561":{"47929833":{"lux":351.62,"IR":3911.0,"ambient":15416.0}}},"program":"simplei2csensors","ipAddress":"192.168.1.23","ts":{"tz":"CDT","time":1527959284.235061}}


Will look into using auth keys ( needs an option in rpi basic setup).. essentially eaters change all EXPEC scripts or using the PROMPT as token to expect password .. that would just send the password and as long as the password is not a linux command it should work

Karl

the expect files all start with:
Code: Select all
set userID [lindex $argv 0 ]
set password [lindex $argv 1 ]
set ipNumber [lindex $argv 2 ]
set ipParms  [lindex $argv 3 ]
set piPath   [lindex $argv 4 ]
set indigoPath   [lindex $argv 5 ]
set timeOUT [lindex $argv 6 ]

set timeout $timeOUT


spawn sftp -o ConnectTimeout=$timeOUT $userID@$ipNumber
 
expect {
    "(yes/no)? " {
        send "yes\r"
        sleep 0.1
        expect "assword: " { send "$password\r"}
    }   
    "assword: " {
        send "$password\r"
    }
}
and yes it is "assword" as sometimes it is Password or password
need to replace "assword: " with "login:" if auth keys are used.


with authkeys on it does:
Code: Select all
mini-12:13:05 ~ 8:ssh pi@192.168.1.23

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Jun  2 12:07:10 2018 from 192.168.1.53
would look for login: in "Last login: Sat J..."

just thinking out load....

Posted on
Sat Jun 02, 2018 11:56 am
shrxman offline
Posts: 46
Joined: Apr 22, 2015

Re: Error: Lets wait for new config files

I think pibeacon thinks it's rebooting the new pi. I see this in the logs:
10:42:41 -RPI# 2 check , too many empty messages in a row: 2
10:42:41 -sending reboot command to RPI
10:43:04 -creating new beacon, received from pi # 3/B8:27:EB:42:BF:21: beacon-4B:3E:E1:33:3D:74 UUID: ff4c000c0e000bfd474ba78a6529-44164-10935
10:43:04 -checkForUpdates in Line '7906' has error='dictionary changed size during iteration'
10:43:25 -creating new beacon, received from pi # 3/B8:27:EB:42:BF:21: beacon-E8:C2:D9:46:50:55 UUID: x-x-x
10:43:45 -send YOUR command to rpi 10.10.10.103; "[{\"cmdLine\": \"ls /home/pi/pibeacon\", \"command\": \"general\"}]"
10:45:00 -RPI# 2 check , too many empty messages in a row: 2
10:45:00 -sending reboot command to RPI
10:45:19 -creating new beacon, received from pi # 3/B8:27:EB:42:BF:21: beacon-65:50:42:5D:16:2E UUID: 000b15bdff5df7757853e4331a0f1005-2832-4192
10:47:01 -RPI# 2 check , too many empty messages in a row: 2
10:47:01 -sending reboot command to RPI

then, when i try to push all files,
pi@officepi:~/pibeacon $ tail -F temp/messageSend
x

i don't think that x marks the spot! :-o

Who is online

Users browsing this forum: No registered users and 1 guest