Page 71 of 78
Re: piBeacon: presence monitoring plugin discussions
Posted:
Sun Oct 20, 2019 9:20 am
by kw123
GlennNZ: could you try this version:
https://www.dropbox.com/s/a7s6bc3rd6lc7id/piBeacon.indigoPlugin.zip?dl=1It should have the gpioinput and the beacon error fixed..
Karl
Re: piBeacon: presence monitoring plugin discussions
Posted:
Wed Oct 23, 2019 4:41 am
by siclark
Hi Karl.
I just lost the ability to edit rPi devices with the latest version from the plugin store. Downgrading to 313 and I could edit again.
This is the error message I got.
Error (client) runDialogForDevice() caught exception: PAXDialogControllerError -- Field ID sleepAfterBootLabel was already used. Every <Field> element must have a unique field ID.
Simon
piBeacon: presence monitoring plugin discussions
Posted:
Wed Oct 23, 2019 5:01 am
by kw123
I know. If have a fix ready but need to get it to github
Normally I do teamviewer session to my mac at home and then do the github stuff. But this time I switched off my mouse and it appears that now the mouse is not usable when dialing in remotely.
Sent from my iPhone using Tapatalk
Re: piBeacon: presence monitoring plugin discussions
Posted:
Wed Nov 13, 2019 10:41 pm
by kw123
got a RDlidar sensor. Those are laser distance sensors that spin around and give a 2 d view of distance of objects (and walls) to the sensor.
The seems to be promising: it can measure when i walk to or from or sideways of it, sees me waving my hand . .. sees direction
Positioning this in the middle of the room (that will be a problem) would allow a nice view of the complete room = measure any movement .. but limited to one height.
The key measurement is: if for n contigous angles the sum(distance_values) > x or < -x . ==> then there is movement
This can be done for current value vs last value or current value vs empty room value. Thats shows permanent changes, not movement
These are better than the PIR / ultrasound / microwave sensor as they show more details and direction.
will try to add this to piBeacon.
Goal is to combine several sensor type to determine presence
anyway... wanted to share my excitement
Karl
Re: piBeacon: presence monitoring plugin discussions
Posted:
Thu Nov 14, 2019 10:44 pm
by kw123
here the first plot with the RD-lidar sensor.
Indicated is the area with movement = hand waving .. and a clear trigger is generated on the RPI with the previously mentioned approach
the green is the "empty room" = calibration , the red is the snapshot at time of movement
some of the red dots do not show as they are below the green dots
Karl
ps the room really looks like this, lots of stuff in there -- my lab
and the sensor is with one side to the wall = no signal
and it does not get signals back on some surfaces
Re: piBeacon: presence monitoring plugin discussions
Posted:
Sun Nov 17, 2019 12:37 am
by mundmc
This is awesome Karl! Following
Re: piBeacon: presence monitoring plugin discussions
Posted:
Sun Nov 17, 2019 8:59 am
by kw123
It’s almost ready ...
Fine tuning the image options
And calibration action
And No soldering needed
Karl.
Sent from my iPhone using Tapatalk
Re: piBeacon: presence monitoring plugin discussions
Posted:
Sun Nov 24, 2019 10:46 am
by yassi
Karl,
after installing the newest plugin version (7.114.322) I have all the time the message(s) below in the log:
24.11.2019, 17:42:02
piBeacon Warning TCPIP socket error rate high for 192.168.100.112/unknown ; previous:2019-11-24 17:42:02
pi TCPIP socket IP name type first last #MSGs #bytes bytes/MSG maxBytes bytes/min MSGs/min
192.168.100.112 none timeout 2019-07-20 15:10:55 2019-11-21 22:24:40 5 0 0 0 0.0 0.00
192.168.100.112 pi_IN_0 ok 2019-01-06 15:02:24 2019-11-24 16:31:37 277417 57316051 206 537 123.2 0.60
192.168.100.112 pi_IN_Alive ok 2019-01-06 15:03:49 2019-11-24 16:30:22 64326 24548378 381 493 52.8 0.14
192.168.100.112 unknown errIP
What to do?
Yassi
Re: piBeacon: presence monitoring plugin discussions
Posted:
Sun Nov 24, 2019 1:50 pm
by kw123
Did the Ip number of your rpi change?
Do you have WiFi and Ethernet on the rpi?
[EDIT]
after looking at the code:
This is a warning that an RPI -ip number is unknown.
This is a filter to reject any messages from unregistered IP#'s (= not registered in the plugin as an RPI in RPI setup)
Karl
Sent from my iPhone using Tapatalk
Re: piBeacon: presence monitoring plugin discussions
Posted:
Mon Nov 25, 2019 12:13 am
by yassi
No, the IP didn‘t changed, same as before.
The Pi is connected via WiFi.
I will try to reboot the Pi.
Sent from my iPhone using Tapatalk
Re: piBeacon: presence monitoring plugin discussions
Posted:
Mon Nov 25, 2019 10:29 am
by kw123
Check:
In terminal ping rpi
In indigo menu initial setup of rpi
Sent from my iPhone using Tapatalk
Re: piBeacon: presence monitoring plugin discussions
Posted:
Mon Nov 25, 2019 1:59 pm
by yassi
Karl,
ok.
1. Pi was reachable on the network.
2. But, to be sure, rebooted the Pi.
3. Initial Setup done &/saved (but didn't sent any config again to the Pi).
Seems so, that the errors disappeared, I will keep an eye on it.
Thanks,
yassi
piBeacon: presence monitoring plugin discussions
Posted:
Mon Nov 25, 2019 2:47 pm
by kw123
The only away that warning shows up is when the registered ip# in the plugin is not the same as the one received from the rpi
I had it that an rpi had 2 ip# and was reachable on the registered but was sending on the other. ..
That might be an dhcp problem.
Karl.
Sent from my iPhone using Tapatalk
Re: piBeacon: presence monitoring plugin discussions
Posted:
Tue Nov 26, 2019 12:15 am
by yassi
Ok.
In my case, there is only one rPi and it’s only connected via WiFi.
But, no errors since yesterday, so it should be fine now.
Yassi
Sent from my iPhone using Tapatalk
piBeacon: presence monitoring plugin discussions
Posted:
Sun Apr 05, 2020 1:18 am
by GlennNZ
- Code: Select all
05-17:05:45 master execMaster L:2074 Lv:30 ========================= starting master version: 12.6
Killed
pi@raspberrypi:~/pibeacon $ nohup: ignoring input and appending output to 'nohup.out'
05-17:05:51 piBeaconUtils writeTZ L:1287 Lv:30 cBY:master changing timezone executing
05-17:05:51 piBeaconUtils writeTZ L:1296 Lv:30 cBY:master Line 1288 has error=global name 'timeZones' is not defined
05-17:05:51 master setupX L:469 Lv:30 startX called action: >>>stop<<<
05-17:05:53 piBeaconUtils writeTZ L:1287 Lv:30 cBY:master changing timezone executing
05-17:05:53 piBeaconUtils writeTZ L:1296 Lv:30 cBY:master Line 1288 has error=global name 'timeZones' is not defined
05-17:05:53 master setupX L:469 Lv:30 startX called action: >>>stop<<<
05-17:05:54 master readNewParams L:380 Lv:30 UPS-V2 interface NOT enabled
05-17:05:55 master setACTIVEorKILL L:548 Lv:30 started:INPUTgpio.py
05-17:05:55 INPUTgpio <module> L:204 Lv:30 starting INPUTgpio program
05-17:05:55 piBeaconUtils writeTZ L:1287 Lv:30 cBY:INPUTgpio changing timezone executing
05-17:05:55 piBeaconUtils writeTZ L:1296 Lv:30 cBY:INPUTgpio Line 1288 has error=global name 'timeZones' is not defined
05-17:06:01 installLibs <module> L:316 Lv:30 installLibs starting
05-17:06:01 installLibs <module> L:343 Lv:30 installLibs no opsys upgrade requested
05-17:06:01 installLibs <module> L:366 Lv:30 ==== libraries seem to be setup, no need for action
05-17:06:01 installLibs <module> L:368 Lv:30 ==== libraries install finished
05-17:06:01 piBeaconUtils writeTZ L:1287 Lv:30 cBY:receiveCommands changing timezone executing
05-17:06:01 piBeaconUtils writeTZ L:1296 Lv:30 cBY:receiveCommands Line 1288 has error=global name 'timeZones' is not defined
05-17:06:01 receiveCommands <module> L:175 Lv:30 proceding with normal on no ad-hoc network
05-17:06:01 receiveCommands <module> L:182 Lv:30 started, listening to port: 9999
05-17:06:02 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:06:02 piBeaconUtils writeTZ L:1296 Lv:30 cBY:beaconloop Line 1288 has error=global name 'timeZones' is not defined
05-17:06:02 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
sudo: /etc/init.d/ntp: command not found
sudo: /etc/init.d/ntp: command not found
05-17:06:03 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:06:03 beaconloop execbeaconloop L:894 Lv:30 starting loop
Hi Karl
Hope all is well and you are surviving the world we find ourselves in...
Had an issue with rpi, replaced SD card, added fan (thought was overheating) Well was overheating, in a sealed box but may be more to it. Replaced SD card with new Buster image.
Had the above error on startup - missing the G from G.timezones in line 1288, piBeaconUtils. Changed, Added that and now working on this error:
- Code: Select all
pi@raspberrypi:~/pibeacon $ sudo python master.py
05-17:09:07 master execMaster L:2074 Lv:30 ========================= starting master version: 12.6
Killed
pi@raspberrypi:~/pibeacon $ nohup: ignoring input and appending output to 'nohup.out'
05-17:09:13 piBeaconUtils writeTZ L:1287 Lv:30 cBY:master changing timezone executing
05-17:09:13 master setupX L:469 Lv:30 startX called action: >>>stop<<<
05-17:09:16 piBeaconUtils writeTZ L:1287 Lv:30 cBY:master changing timezone executing
05-17:09:16 master setupX L:469 Lv:30 startX called action: >>>stop<<<
05-17:09:17 master readNewParams L:380 Lv:30 UPS-V2 interface NOT enabled
05-17:09:18 master setACTIVEorKILL L:548 Lv:30 started:INPUTgpio.py
05-17:09:18 INPUTgpio <module> L:204 Lv:30 starting INPUTgpio program
05-17:09:18 piBeaconUtils writeTZ L:1287 Lv:30 cBY:INPUTgpio changing timezone executing
05-17:09:23 installLibs <module> L:316 Lv:30 installLibs starting
05-17:09:23 installLibs <module> L:343 Lv:30 installLibs no opsys upgrade requested
05-17:09:23 installLibs <module> L:366 Lv:30 ==== libraries seem to be setup, no need for action
05-17:09:23 installLibs <module> L:368 Lv:30 ==== libraries install finished
05-17:09:24 piBeaconUtils writeTZ L:1287 Lv:30 cBY:receiveCommands changing timezone executing
05-17:09:24 receiveCommands <module> L:175 Lv:30 proceding with normal on no ad-hoc network
05-17:09:24 receiveCommands <module> L:182 Lv:30 started, listening to port: 9999
05-17:09:24 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
sudo: /etc/init.d/ntp: command not found
05-17:09:24 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
sudo: /etc/init.d/ntp: command not found
05-17:09:26 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:09:26 beaconloop execbeaconloop L:894 Lv:30 starting loop
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:09:48 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:09:49 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:09:50 piBeaconUtils restartMyself L:129 Lv:30 echo 1 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:09:50 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:09:51 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:09:51 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
05-17:09:53 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:09:53 beaconloop execbeaconloop L:894 Lv:30 starting loop
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:10:12 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:10:13 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:10:14 piBeaconUtils restartMyself L:129 Lv:30 echo 2 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:10:14 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:10:14 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:10:14 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
05-17:10:16 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:10:16 beaconloop execbeaconloop L:894 Lv:30 starting loop
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:10:28 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:10:29 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:10:30 piBeaconUtils restartMyself L:129 Lv:30 echo 3 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:10:30 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:10:30 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:10:31 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
05-17:10:32 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:10:32 beaconloop execbeaconloop L:894 Lv:30 starting loop
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:10:46 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:10:47 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:10:48 piBeaconUtils restartMyself L:129 Lv:30 echo 4 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:10:48 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:10:48 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:10:49 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
05-17:10:50 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:10:50 beaconloop execbeaconloop L:894 Lv:30 starting loop
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:11:04 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:11:05 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:11:06 piBeaconUtils restartMyself L:129 Lv:30 echo 5 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:11:06 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:11:06 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:11:07 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
05-17:11:08 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:11:08 beaconloop execbeaconloop L:894 Lv:30 starting loop
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:11:36 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:11:37 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:11:38 piBeaconUtils restartMyself L:129 Lv:30 echo 6 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:11:38 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:11:38 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:11:39 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
05-17:11:40 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:11:40 beaconloop execbeaconloop L:894 Lv:30 starting loop
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:11:58 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:11:59 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:12:00 piBeaconUtils restartMyself L:129 Lv:30 echo 7 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:12:00 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:12:01 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:12:01 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
05-17:12:02 beaconloop startBlueTooth L:222 Lv:30 ble thread started
05-17:12:02 beaconloop execbeaconloop L:894 Lv:30 starting loop
05-17:12:16 piBeaconUtils writeTZ L:1287 Lv:30 cBY:master changing timezone executing
05-17:12:16 master setupX L:469 Lv:30 startX called action: >>>stop<<<
05-17:12:16 master readNewParams L:380 Lv:30 UPS-V2 interface NOT enabled
05-17:12:20 piBeaconUtils writeTZ L:1287 Lv:30 cBY:INPUTgpio changing timezone executing
rm: cannot remove '/home/pi/pibeacon/temp/stopBLE': No such file or directory
05-17:12:22 beaconloop execbeaconloop L:982 Lv:50 in Line 973 has error=timed out.. sock.recv error, likely time out
05-17:12:23 piBeaconUtils restartMyself L:109 Lv:50 cBY:beaconloop --- restarting --- sock.recv error
05-17:12:24 piBeaconUtils restartMyself L:129 Lv:30 echo 8 > /home/pi/pibeacon/temp/restartLast.beaconloop
05-17:12:24 piBeaconUtils restartMyself L:135 Lv:30 sudo /usr/bin/python /home/pi/pibeacon/beaconloop.py &
05-17:12:25 piBeaconUtils writeTZ L:1287 Lv:30 cBY:beaconloop changing timezone executing
05-17:12:25 beaconloop startBlueTooth L:127 Lv:30 (re)starting bluetooth
Thanks
The /etc/init.d/ntp seems relevant as never seems to correctly change timezone, raspi-config timezone set same as Mac as instructed.
Edit:
Did manage to Apt-get ntp - which seems to have fixed the Timezone error... (was the buster pibeacon image)
Still getting the stopBLE file not found error though.. will create a file so-named and see what happens...
Seems all good after those changes!
Glenn