piBeacon: 7- tested Beacons

Yes that plugin.log

After you run the menu/detect... it takes about 30 secs to show up in the logfile.


Sent from my iPhone using Tapatalk

This is all I have in that file. Run the detect multiple times this afternoon

Code: Select all


16:11:05                          -myLogSet setting parameters -- logFileActive= ; logFile= /Library/Application Support/Perceptive Automation/Indigo 7.2/Preferences/Plugins/com.karlwachs.piBeacon/plugin.log;  debugLevel= []
16:12:25                          -myLogSet setting parameters -- logFileActive= ; logFile= /Library/Application Support/Perceptive Automation/Indigo 7.2/Preferences/Plugins/com.karlwachs.piBeacon/plugin.log;  debugLevel= []
16:12:25                          - --V 7.103.272     initializing  --
16:15:47                          -myLogSet setting parameters -- logFileActive= ; logFile= /Library/Application Support/Perceptive Automation/Indigo 7.2/Preferences/Plugins/com.karlwachs.piBeacon/plugin.log;  debugLevel= []
08:57:15 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
08:57:15                          -169.254.30.112  unknown      errIP      2019-02-24 08:57:15 2019-02-24 08:57:15         1            0         0         0       0.0      0.00
08:57:18 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
08:57:18                          -169.254.30.112  unknown      errIP      2019-02-24 08:57:15 2019-02-24 08:57:18         2            0         0         0       0.0      0.00
08:57:21 pi TCPIP socket          -IP              name          type      first               last                    #MSGs       #bytes bytes/MSG  maxBytes bytes/min  MSGs/min
08:57:21                          -169.254.30.112  unknown      errIP      2019-02-24 08:57:15 2019-02-24 08:57:21         3            0         0         0       0.0      0.00



Actually, why does this say

Code: Select all

logFile= /Library/Application Support/Perceptive Automation/Indigo [b]7.2[/b]/Preferences/Plugins/com.karlwachs.piBeacon/plugin.log

I am on 7.5 and dont have. a 7.2 folder.

I got that error too when the data send is too long,

could you set the rssi min to -50 then run again?

you should see something like this:

Code: Select all

===================== existing_Beacons ====================    char pos    01  23 45 67 89 A1 23 45 67 89 B1 01 23 45 67 89 C1 23 45 67 89 D1 23 45 67 89 E1 23 45 67 89 F1
===MAC# 1F:71:45:70:82:1E  -b-nutF-3
tag ----------        msg-Type : raw data: preamble->   [-- mac # ------] dat ll   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 .. RSSI
NutFinder               Nmsg:16: 04 3E 28 02 01 00 00   1E 82 70 45 71 1F     1C  02 01 06 03 03 03 18 05 FF D2 00 00 33 09 16 0A 18 1F 71 45 70 82 1E 04 09 6E 75 74             DE=-34
                      Flags-01 : 06
             16BServClcmplt-03 : 0318
                       Name-09 : nut
                ServiceData-16 : 0A181F714570821E
                       UUID-FF : D2000033-
                    pos_of_MAC : 18
n_of_MSG_Types                 : 1
MSG_in_10Secs                  : 6.4
max_rssi                       : -17
max_TX                         : -99


and re logfile, in config, could you set the logfile at the bottom. the path is setup dynamically. you might have an old setting there
... will force the setting in the next version (no option, nothing to set)

Karl

I had been looking under the log in Preferences, but do you mean the plugin.log here?

/Volumes/Perceptive Automation/Indigo 7.5/Logs/com.karlwachs.piBeacon/plugin.log

.... /Perceptive Automation/Indigo 7.5/Logs/com.karlwachs.piBeacon/plugin.log

yes

Karl

Here you go.

Code: Select all

===MAC# FF:93:06:A3:BB:E6  -piBeacon - Car Key Grey
tag ----------        msg-Type : raw data: preamble->   [-- mac # ------] dat ll   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 .. RSSI
other                   Nmsg:12: 04 3E 28 02 01 00 01   E6 BB A3 06 93 FF     1C  02 01 06 03 03 03 18 05 FF 59 00 00 46 09 16 0A 18 FF 93 06 A3 BB E6 04 09 6E 75 74             BC=-68
                      Flags-01 : 06
             16BServClcmplt-03 : 0318
                       Name-09 : nut
                ServiceData-16 : 0A18FF9306A3BBE6
                       UUID-FF : 59000046-
                    pos_of_MAC : 18
n_of_MSG_Types                 : 1
MSG_in_10Secs                  : 4.8
max_rssi                       : -65
max_TX                         : -99

===MAC# C7:90:40:FC:10:6F  -piBeacon - Car Key White
tag ----------        msg-Type : raw data: preamble->   [-- mac # ------] dat ll   1  2  3  4  5  6  7  8  9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 .. RSSI
other                   Nmsg:13: 04 3E 28 02 01 00 01   6F 10 FC 40 90 C7     1C  02 01 06 03 03 03 18 05 FF 59 00 00 46 09 16 0A 18 C7 90 40 FC 10 6F 04 09 6E 75 74             BC=-68
                      Flags-01 : 06
             16BServClcmplt-03 : 0318
                       Name-09 : nut
                ServiceData-16 : 0A18C79040FC106F
                       UUID-FF : 59000046-
                    pos_of_MAC : 18
n_of_MSG_Types                 : 1
MSG_in_10Secs                  : 5.2
max_rssi                       : -65
max_TX                         : 116

that looks correct
please check your nut application if all parameters are set the same ie set alarm off

ssh to the RPi the nut is closest
tail -f /var/log/pibecon
the send a beep command that RPI

you should see something like:

Code: Select all

11-16:25:38 execcommands    execCMDS             L:384  Lv:20 execcmd. beep, write: ={"1F:71:45:70:82:1E": {"cmdOff": ["char-write-req 0x0025 03"], "random": "public", "mustBeUp": false, "cmdON": ["char-write-req 0x0025 04"], "beepTime": 1.0}}
11-16:25:40 beaconloop      beep                 L:3440 Lv:20 beepBeacon devices:{u'1F:71:45:70:82:1E': {u'cmdOff': [u'char-write-req 0x0025 03'], u'random': u'public', u'mustBeUp': False, u'cmdON': [u'char-write-req 0x0025 04'], u'beepTime': 1.0}}
11-16:25:40 beaconloop      beep                 L:3457 Lv:20 sudo /usr/bin/gatttool -i hci1   -b 1F:71:45:70:82:1E -I
11-16:25:40 beaconloop      beep                 L:3461 Lv:20 ... successful: [1F:71:45:70:82:1E][LE]->
11-16:25:40 beaconloop      beep                 L:3483 Lv:20 1F:71:45:70:82:1E:   cmdON:[u'char-write-req 0x0025 04'];  cmdOff:[u'char-write-req 0x0025 03'];  beepTime:1.0
11-16:25:40 beaconloop      beep                 L:3489 Lv:20 expect connect
11-16:25:42 beaconloop      beep                 L:3493 Lv:20 ... successful: Connection successful
11-16:25:42 beaconloop      beep                 L:3520 Lv:20 sendline  cmdchar-write-req 0x0025 04
11-16:25:42 beaconloop      beep                 L:3524 Lv:20 ... successful:
[-1F:71:45:70:82:1E
11-16:25:43 beaconloop      beep                 L:3540 Lv:20 sendline  cmdchar-write-req 0x0025 03
11-16:25:43 beaconloop      beep                 L:3544 Lv:20 ... successful: ][LE]> char-write-req 0x0025 04
[-1F:71:45:70:82:1E
11-16:25:44 beaconloop      beep                 L:3553 Lv:20 sendline disconnect
11-16:25:44 beaconloop      beep                 L:3556 Lv:20 ... successful: >


try that with the nut that works and the one that does not work

Karl

Sorry for misunderstanding but neither works.

Code: Select all

 
11-22:31:08 execcommands    execCMDS             L:384  Lv:20 execcmd. beep, write: ={"C7:90:40:FC:10:6F": {"cmdOff": ["char-write-req 0x0025 03"], "random": "public", "mustBeUp": false, "cmdON": ["char-write-req 0x0025 04"], "beepTime": 5.0}}
11-22:31:10 beaconloop      beep                 L:3440 Lv:20 beepBeacon devices:{u'C7:90:40:FC:10:6F': {u'cmdOff': [u'char-write-req 0x0025 03'], u'random': u'public', u'mustBeUp': False, u'cmdON': [u'char-write-req 0x0025 04'], u'beepTime': 5.0}}
11-22:31:10 beaconloop      beep                 L:3457 Lv:20 sudo /usr/bin/gatttool -i hci0   -b C7:90:40:FC:10:6F -I
11-22:31:10 beaconloop      beep                 L:3461 Lv:20 ... successful: [C7:90:40:FC:10:6F][LE]->
11-22:31:10 beaconloop      beep                 L:3483 Lv:20 C7:90:40:FC:10:6F:   cmdON:[u'char-write-req 0x0025 04'];  cmdOff:[u'char-write-req 0x0025 03'];  beepTime:5.0
11-22:31:10 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:31:25 beaconloop      beep                 L:3499 Lv:20 ... timeout, try again:  connect
Attempting to connect to C7:90:40:FC:10:6F
[C7:90:40:FC:10:6F][LE]> -<class 'pexpect.exceptions.TIMEOUT'>
11-22:31:26 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:31:41 beaconloop      beep                 L:3499 Lv:20 ... timeout, try again:  connect
Attempting to connect to C7:90:40:FC:10:6F
[C7:90:40:FC:10:6F][LE]> connect
[C7:90:40:FC:10:6F][LE]> -<class 'pexpect.exceptions.TIMEOUT'>
11-22:31:42 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:31:50 beaconloop      beep                 L:3498 Lv:20 ... error, try again:  connect
Attempting to connect to C7:90:40:FC:10:6F
[C7:90:40:FC:10:6F][LE]> connect
[C7:90:40:FC:10:6F][LE]> connect
-Error
11-22:31:51 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:32:06 beaconloop      beep                 L:3499 Lv:20 ... timeout, try again: : connect error: Connection refused (111)
[C7:90:40:FC:10:6F][LE]> connect
Attempting to connect to C7:90:40:FC:10:6F
[C7:90:40:FC:10:6F][LE]> -<class 'pexpect.exceptions.TIMEOUT'>
11-22:32:07 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:32:22 beaconloop      beep                 L:3499 Lv:20 ... timeout, try again: : connect error: Connection refused (111)
[C7:90:40:FC:10:6F][LE]> connect
Attempting to connect to C7:90:40:FC:10:6F
[C7:90:40:FC:10:6F][LE]> connect
[C7:90:40:FC:10:6F][LE]> -<class 'pexpect.exceptions.TIMEOUT'>
11-22:32:23 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:32:33 beaconloop      beep                 L:3510 Lv:20 connect error, giving up
11-22:32:33 beaconloop      beep                 L:3457 Lv:20 sudo /usr/bin/gatttool -i hci0   -b C7:90:40:FC:10:6F -I
11-22:32:33 beaconloop      beep                 L:3461 Lv:20 ... successful: [C7:90:40:FC:10:6F][LE]->
11-22:32:34 beaconloop      beep                 L:3483 Lv:20 C7:90:40:FC:10:6F:   cmdON:[u'char-write-req 0x0025 04'];  cmdOff:[u'char-write-req 0x0025 03'];  beepTime:5.0
11-22:32:34 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:32:49 beaconloop      beep                 L:3499 Lv:20 ... timeout, try again:  connect
Attempting to connect to C7:90:40:FC:10:6F
[C7:90:40:FC:10:6F][LE]> -<class 'pexpect.exceptions.TIMEOUT'>
11-22:32:50 beaconloop      beep                 L:3489 Lv:20 expect connect
11-22:33:05 beaconloop      beep                 L:3499 Lv:20 ... timeout, try again:  connect
Attempting to connect to C7:90:40:FC:10:6F
[C7:90:40:FC:10:6F][LE]> connect
[C7:90:40:FC:10:6F][LE]> -<class 'pexpect.exceptions.TIMEOUT'>
11-22:33:06 beaconloop      beep                 L:3489 Lv:20 expect connect


ok so it can not connect. that SHOULD mean that the iPhone still OWNS it = not other device can connect -- these devices can only have one master at a time.

make sure the nut app is not active - also not in the background on your phone

then please check the nut app parameters: mine look like:

This one had never been connected to the Nut app but I’ve now done so to grab the identifiers. I’ve killed app in background as well.
Appears different hardware and firmware.

I guess that means we have to go down to the command line.
Can we do an online session?
I am on dallas time.


Sent from my iPhone using Tapatalk

Sure. thank you PMd you.

Hi all,

Anyone know what's the trick to getting the Nonda Aiko to work correctly?

I took one out of the box, charged it. Told PiBeacon to accept any Nondas, pushed the (hidden) button, it beeped. Beacon appeared in Indigo. Renamed, moved to a different folder.

Beacon goes down after several minutes. Will wake up if I push the button, but that's not the desired behavior.

I did not connect to it with any kind of app from Nonda, or even a BLE scanner. I assumed I should disregard all the instructions that came with it about pairing to the phone and all that, since we're not using their software.

I had a similar experience with iTag beacons (they work for a while, then stop broadcasting), which is why I decided to try Nonda Aiko. Seems nothing works as well as the Social Retail beacons that I use in the cars, but they are way too large for other purposes.

Any clues, please let me know what to try. Thanks!