1. bugfix: "plugin.py", line 20656, in actionControlSensor type: name 'address' is not defined
2. added option to not print test logging at startup, set in config/ debug section

added cut off values for distance sensors min/ max, added state distanceRaw (unmodified measured value)

Added features / changes in v2022.165.69@ 2023-04-01

1. added support for thermobeacons. They are bluetooth temperature & humidity sensors w and w/o display they are sold under various brands like sensorBlue etc.

2. added some states to itrack button: state of beacon current and last off event time stamp

3. for BLE-sensor devcies added pluginProp beaconDevId that is the corresponding beacon device to the sensor device eg for on off BLE sensor device like iTrack it has a corresponding beacon device that has the same MAC number this can be used in triggers etc to find which device triggered

4. added variables: lastButtonOnDevId this is the device id of an on/off BLE sensor device that was off-> on lastButtonOnBeaconDevId this is the corresponding dev id for the beacon device this can be used eg after receiving an On event from an iTrack sensor on/off device to send a message to the beacon to make it beep or get battery level like so in an action script:

#

#

#

this action:

calls actiongroup to open door, but not more often than every 10 secs

then send get battery command to rpi # 999 (closeset) for corresponding beacon that triggered the button

it has 3 lists of triggering devices, will do something else for group B, C

#

this is the list of on/off button BLE devices that could have triggerd this action

we have 2 lists, different actions for A and B

you can use names or variables

devListA = ["button-musegear-1", "button-musegear-2", ] devListB = [ "button-musegear-H", ] devListC = [ "button2"]

if you want to use Ids

devListA = [123,23524,56745,457457 ]

devListB = [2453456,6475789,231234124]

devListC = [2453456,6475789,231234124]

beep = True getBattery = True

import time

is everything running?:

try: plug = indigo.server.getPlugin("com.karlwachs.piBeacon") except: indigo.server.log("plugin not running") return if not plug.isEnabled(): indigo.server.log("plugin not running") return

get device that triggered this action:

try: triggerDevId = indigo.variables["lastButtonOnDevId"].value triggerDev = indigo.devices[int(triggerDevId)] except: indigo.server.log("variable lastButtonOnDevId:{} not correct".format(triggerDevId)) return

if type(devListA[0]) == type(1): useTag = triggerDev.id else: useTag = triggerDev.name

if useTag not in devListA + devListB + devListC: indigo.server.log("trigger device {} not in defined groups".format(triggerDev.name)) return

action for A list

if useTag in devListA or useTag in devListB: # get / setup last time stamp variable of last action for this action try: var = indigo.variables["lastDoorOpen"].value except:
indigo.variable.create("lastDoorOpen","0") var = indigo.variables["lastDoorOpen"].value lastOpen = float(var)

if time.time() - lastOpen > 10: # too early for this action?
    indigo.actionGroup.execute("press door unlock button action")  # use your action here 
    indigo.variable.updateValue("lastDoorOpen", value="{:.0f}".format(time.time())) # remember last action in variable
else: # skip
    indigo.server.log("skipping open door, last open door event was {:.0f} secs ago".format(time.time()-lastOpen))
    return 

# now next action, beep and get battery level
beacondevID = indigo.variables["lastButtonOnBeaconDevId"].value
try:
    beaconDev = indigo.devices[int(beacondevID)]
except:
    indigo.server.log("beacon {}  not defined in indigo".format(beacondevID))
    return 

if beep:    # server =-1: use closest, beepTime =-1: only beep off, >0 = beep 
    plug.executeAction("beepBeacon", props ={"piServerNumber":"-1","selectbeacon": beacondevID,"beepTime":"1"})
    indigo.server.log("sending beep to dev:{}".format(beaconDev.name))
if getBattery:  # must "set get battery mode" to interactive in config                          
    indigo.server.log("sending get battery to dev:{}".format(beaconDev.name)) 
    # all = use closest RPI, startAtDateTime set delay of start for command, 0 should work fine 
    plug.executeAction("getONEiBeaconParameters", props ={"piServerNumber":"all","devIdOfBeacon": beacondevID, "startAtDateTime":0})

action for C list do beep and then 9 sec ater get battery level

if useTag in devListC: beacondevID = indigo.variables["lastButtonOnBeaconDevId"].value beaconDev = indigo.devices[int(beacondevID)] plug.executeAction("beepBeacon", props ={"piServerNumber":"-1","selectbeacon": beacondevID,"beepTime":"1"}) plug.executeAction("getONEiBeaconParameters", props ={"piServerNumber":"all","devIdOfBeacon": beacondevID, "startAtDateTime":0})

#

#

#

fixed some issues with new iTrack beacons.

1. added new dev type iTrack (Rinex,Vozni,Njoii,Musegear) BUTTON. iTrack types are regular beacon that can deliver battery info, can be beeped and can trigger any indigo action with the button press !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!! FINALLY an ALL IN ONE device - after 8 years with this plugin: beacon position, Battery level, beep, and action button. !!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

   1. get a iTrack beacon, (amazon germany euro 25 for Musegear),
   2. click on the button for 5 secs to enable it
   3. add the eg musegear beacon to indigo: menu/ accept/reject new beacons, select ITrack: Rinex,Vozni,Njoii,Musegear On Button as beacon type; then a new beacon will be created within 30 secs. Copy the mac number
   4. add a new device type "BLE-iTrack (Musegear,Rinex,..) On Button", paste the mac number. Select which rpi should track the button sensor button On/off ( this is not the beacon data!!, that will continue as is)
   5. then you can press the button (5 secs) on the beacon and the status will go to "true/On" for 30 secs, then to false/off again, use this as a trigger to eg open door...

   ===== now you can with this beacon type:

   1. know in which room the beacon is (requires one rpi per room, state= closest RPI ), or if it is away or if it moves - change in distances states, or dev state position of beacon
   2. you can see the battery level in the beacon dev state
   3. you can in indigo menu/action beep the beacon to find it

      4. press the button on the beacon and you can trigger any action in indigo

   The smallest version is 4mm x 35mm x 25mm There are regular, wallet, mini, rechargeable versions

2. added support for the new indigo 2022.2 http api w bearer id. the old http restfull api does not work under indigo 2022.2 the new version will only work if your RPI is running bullseye or later and everything with py3 BUT it will create a lot of logfile entries each time the rpis send data to indigo. with the old version there was a patch you could use to disable the logging.

   I strongly recommend to use the default socket communication rpi to indigo - you select it in config. that works with all versions and combinations

3. worked on "fastDown" option for beacons. It is now stable down to 10 secs. Normal mode beacons take about 90 secs to go "down"/ off. They expire due to no signal receives from rpis in indigo In fastdown mode the rpi sends a signal (down rssi=-999) when it has not received a signal from the beacon for xx secs. After receiving a down signal the plugin sets the state to down - after all rpis have send the down signal. This works for fastDown times down to 15 secs and if you have several RPi that "see" the beacon down to 10 secs. this will create a lot more traffic from the RPIs to the plugin:
   For fastDown time = 10 secs one message every 5 secs from each RPI for each of these fastDown beacons, so for 5 beacons and 5 rpi up to 5 message per second from rpis to indigo Indigo is able to handle this if you have a good sized mac - my mac mini M1 2020 has 14% total load (and 10% pibeacon plugin load on one proc.) with that config with many other plugins running

4. fixed variable counters for devices Up/down for groups with beacon members (the group BEACON was correct). the other groups (Family ..) worked correctly for sensor devcies added 2 more optional groups you can use to count devices home/away, default are Family, guest, other1.. other5. If not assigned a name in config, the variables are not created. You need to edit a device and check the groups name you want it to be come a member of. Then the variables GroupName_Away and _Home counters will be updated

5. fixed: piBeacon Error 'local variable 'xx' referenced before assignment'

1. added new dev type iTrack (Rinex,Vozni,Njoii,Musegear) BUTTON. iTrack types are regular beacon that can deliver battery info, can be beeped and can trigger any indigo action with the button press !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!! FINALLY an all in one device - after 8 years with this plugin. !!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

   1. get a iTrack beacon, (amazon germany euro 25 for Musegear),
   2. click on the button for 5 secs to enable it
   3. add the eg musegear beacon to indigo: menu/ accept/reject new beacons, select iTrack .. Rinex, .. , Musegear as beacon type; then a new beacon will be created within 30 secs. Copy the mac number
   4. add a new device type BLE-iTrack-Button, paste the mac number. Select which rpi should track the button sensor button On/off ( this is not the beacon data!!, that will continue as is)
   5. then you can press the button (5 secs) on the beacon and the status will go to "true/On" for 30 secs, then to false/off again

   ==== now you can with this beacon:

   1. know in which room the beaocn is (requires one rpi per room state= closest RPI ), or if it is away or if it moves - change in distances states, or dev state position of beacon
   2. you can see the battery level in the dev state
   3. you can in indigo menu/action beep the beacon to find it
   4. press the button on the beacon and you can trigger any action in indigo

   The smallest version is 4mm x 35mm x 25mm There are regular, wallet, mini, rechargeable versions

2. added support for the new indigo 2022.2 http api w bearer id. the old http restfull api does not work under indigo 2022.2 the new version will only work if your RPI is running bullseye or later and everything with py3 BUT it will create a lot of logfile entries each time the rpi send data to indigo. with the old version the was a patch you could use to disable the logging.

   I strongly recommend to use the default socket communication rpi to indigo - you select it in config. that works with all versions and combinations

3. worked on "fastDown" option for beacons. It is now stable down to 10 secs. Normal mode beacons take about 90 secs to go "down"/ off. They expire due to no signal receives from rpis in indigo In fastdown mode the rpi sends a signal (down rssi=-999) when it has not received a signal from the beacon for xx secs. After receiving a down signal the plugin sets the state to down - after all rpis have send the down signal. this works for fastDown times down to 15 secs and if you have several RPi that "see" the beacon down to 10 secs. this will create a lot more traffic from teh RPIs to the plugin:
   for fastDown time = 10 secs one message every 5 secs from each RPI for each of these fastDown beacons, so for 5 beacons and 5 rpi up to 5 message per second from rpis to indigo Indigo is able to handle this if you have a good sized mac - my mac mini M1 2020 has 14% total load (and 10% pibeacon plugin load on one proc.) with that config with many other plugins running

1. added color knight rider option for neopixel: you can show swinging LEDS w different colors on a neopixel string for detail see menu/print various info to logfile /print distance actions ..

2. fixed : undervoltage reporting, vcgencmd cmd has moved in new raspian image to /usr/bin/vcgencmd it will check the old and new postion of executable.

This version now offers to directly show distance sensor information on attached neopixel devices on the rpi It does not have to go through indigo. you configure a) the neopixel output device in indigo, set the pyhical parameters - # of LED etc, connect teh device to the RPI b) configure the distance sensor in indigo (any of the supported models3 work) and connect the distance sensor to the same RPI configure the neopixel commands (see menu/indigo/pibeacon/print various info.. for examples) in the distance sensor device like: distance limits for versyshort, short, medium, long verylong and stopped then the distance sensor will send these commands directly to the neopixel.py program on the same RPI when it reaches the limits set, eg stop, verylong distance ... you can have the neopixel device show simple colored LEDS R/B/B or blinking or "knightrider" type the neopixel indigo device status will also show the commands send to it on the rpi

1. improved trigger for distance sensors (how often new values get send to indigo) now it is trigger: if (delta absolut > DA and delta% > D% ) or delta time > 30 secs : send to indigo DA, D% = set in sensor edit added dev state trigger to distance sensor with these setting you can now fine tune trigger sensitivity there is also the option for local execution of any script on the rpi eg set LED lights r/g/b if distance is gt or lt xx... must have neopixel device attached on that RPI do menu /Print various info to logfile../Print Distance action help to logfile/ or click on help button in distance sensors

2. fixed status column method. only ON/off was used. now if detailed colors are set then they are used, on/off only if details not defined. added data field "trigger" send to indigo if there is an action trigger event (Short, Med, Long, Stop, Dist, Time ) you can trigger on that device state["trigger"] == "your choice here" added option to have neopixel return command type received. you must supply "ststus":"yourtext" to the command send to neopixel, eg: echo '{"repeat":"1","status":"Long","command":[{"type":"sLine","display":"wait","position":[0,12,0,0,0]},{"type":"sLine","display":"immediate","position":[0,12,0,100,0]}]}' > temp/neopixel.inp would set neopixle device status to "Long" added states: trigger --> Dist,Time, distanceEvent distanceEvent --> VeryLong,Long,Medium,Short,VeryShort,Stop

3. added line type sLine for neopixel, same as "line" (2D) but just 1D, reduces the number or parameters to be specified

4. reduced key length for specifc commands (long form still works) sLine —> sl line —> l resetinitial -> res knightrider -> kr position -> p spoint -> sp rectangle —> r and repeat:1 is default, no need to add to command display:"immediate" is default, no need to add to command

5. added option to show distance as thermometer type on neopixel, executed locally on RPI

6. added action to pause any distance sensor. it simply "sleeps" in the execution loop for the specified time this is useful if you have local display/neopixel commands and want to pause them due to eg garage dooor open...

fixed bug introduced in v ..19, error setting up new RPI

fixed bug introduced in v ..19, error setting up new RPI

1. added feature kight rider for neopixel (swinging band of leds left right )

1. delay start time for gpio and i2c-relay: now checks ALSO during delay before any action if it should be cancelled in general you can remove the previous command by issuing a new one eg send 10 pulses 1 sec each and then an off after 5 secs, only 5 pulses will be done before this it was only checking during the active part if it should stop. ... this matters only if you use a delay at start parameter

2. bug fix: File "plugin.py", line 6052, in filterNeopixeldevices it is a format error

3. some menu changes

1. added option for each pi to ignore known_hosts for ssh and sftp to rpi this is to avoid needing to modify knownhostsfile incase of changes in ip number etc.

2. fixed pmairquality py2 -> py3 bug ( concatenate strings / bytes) sensor now only works with py3 !!

3. bug for sensor INPUTpulse, device statename was wrong (typo), fixed (bug was added in py2->py3 conversion (u"xxx" changed to "uxxx" instead of "xxx"))

improved switchbot response time by ~ 0.5 secs

fixed issues with py3 ie for BLE connect devices like xiaomi soil meter, Temp&Humidity sensors...

1. made all major py programs on rpi run under python2 or python3 py2 vs py3 can be selected in config for all rpi or left to each individual rpi in rpi dev edit the py version can be selected if in config it is set to individual rpi py3 requires pi-os >=10 (stretch ssd) to work properly

   All required libs are installed by the plugin system (ie neopixel, sensor libs etc, see checkForInclude-py2/py3.py on the rpi eg libs: io, hcidump, smbus2 pexpect, expect, ... , syntax changes: / vs // (int//float), print /;print() etc the devil is in the details:
   calling py3 modules can be different from py2 eg to make them "unlinked" /E option has to be used and many more "little" changes binary socket data transfer is different

   ==> this was a major pice of work <==

   for ssd updates: I suggest that you do

   1. updates apps and sys: sudo apt update sudo apt upgrade -y ( or a more thorough, but mostly not needed: sudo apt dist-upgrade -y )
   2. cleanup: sudo apt autoremove sudo apt clean
   3. then reboot every 2 months to keep the security patches up to date

2. added option to detect new beacons looking at the manufacturer name in the BLE message. Some beacons send that info in their BLE msg some beacons like from NUT or april have several tag definitions, with this option you can catch them all the plugin will then find the proper individual tag that works for the soecific beacon type ie beep, battery, .. to use this: select in "accept new beacons" menu item

3. added TOF sensor vl503l1xDistance. It has range up to 4 m you now can use several of vl503l1x or vl503l0x tof sensors on one RPI

4. several smaller fixes and improvements

5. some menu fixes

1. made switchbot operation work more smoothly, timing, error recovery ..

2. added an action that stops any switchbot actions pending on an rpi eg when you got multiple triggers and the first responding action worked, no need to have the action executed many times like when the door is open no need to trigger open magnet n times more

3. added option in the switchbot action to have a sensor(BLE only) on one RPi that triggers a switchbot action on another (or same) rpi w/o indigo being up. the sensor RPI will send a command to the switchbot rpi through sftp eg a BLE sensor with button press signal (eg ibs04-button) can be received on rpi-1, rpi-1 sends a press/on command to rpi-2 for a switchbot to move the arm. Indigo is not involved. This is useful if the button is out of reach of the rpi where the switchbot is managed and indigo is down To setup create an action in indigo "Set switchbot relay to on/off or pulses.."

4. added option to have ON/OFF sensors stay longer ON for xx secs. Some of these sensors go from on-off within 0.2 secs. This gives the indigo dev state more time to show the ON state

5. added option for on/off sensor to show arbitrary text in display like moving / stopped etc.

6. added support for musegear finder beacons (regular, mini, wallet). They can be purchased from amazon in Europe They can be beeped (to find its location) and the plugin gets the battery level. They have the itrack software similar to Rinex, Njoii, Spotypal etc, which can be bought in the USA

6.1 added support for NUT - pro beacon

1. Added a virtual device "garage door". (similar to the virtual device Car) This dev type tracks the states of a garage door: Closed, opening, stopped, open, closing, position This device needs 3 on/off magnet sensors(eg switchbot connect) and several magnets The sensors are positioned at: at closed position, open position; on the moving door Magnets are at:

   • One on door, moving between open sensor and closed sensor to indicate open/closed
   • Several magnets on the rail where the sensor on the door moves by and gets triggers by the magnets the magnets should be placed >1 "second" apart, something like 20-30 cm But the speed of the door changes, eg at close it slows down. There the magnets should be closer together But not too close as the sensor might not be ready for the next trigger With these magnets the plugin counts the magnets passed and calculates the current position (0-100%)

   The dev states used for the sensors are onoffState and one that indicates the moving changes eg lastMotion of the sensor that is mounted on the door.

2. for ADS-1115 ADC added samples per second option, removed un-used code and made differential measurement (eg input0 -input1)
   a single measurement instead of 2 single and then subtract

1. fixed: value transformation for adc type sensor 1/value was off by factor of 10 (11/value instead of 1/value)
2. made BLEconnect devices work again ie iphones using BLE ping from rpi to phone

1. fixed: BLEconenct "display status error message
2. fixe: cmd0, cmds not found error messages

improved coexistance of trugveg ... and switchbot devices switchbot has better priority now, wait time for trugveg to finish is now max 4 secs, down from 15.

increased speed to switchbot relay and more reliable added autocreate for iSensor devices likt ruuvitag

1. fixed "execSshToRPI @line 18578: 'ret, err = self.readPopen(cmd0)'" left over from py2-py3 conversion
2. added better auto create for certain dev types: switchbot, ruuvi, govee, ...
3. streamlined dev states changed5minutes changed1hour ... does not store values in dev props but in file (changedValues.json) in pluginPrefs directory. That gives significant reduction in device restarts = reduced load in plugin and server
4. removed unicode indicator u" (now just " ). removed any unicode() fucntion leftover from python2, ===> now no going back to py2 <===
5. made sure all mac numbers are upper case ie not f9:... but F9:...

1. fixed BLEconnect program on RPi, iPhones are not supported anymore as they do not answer BLE pings anymore, only BLE connect sensors and switches like switchbot.
2. suppressed matplot logging in beacon plot

1. fixed BLEconnect program on RPi, iPhones are not supported anymore as they do not answer BLE pings anymore, only BLE connect sensors and switches like switchbot.
2. supressed matplot logging in beacon plot

1. streamlined and improved autocreate of BLE sensors type device (temp, humidity, pressure, motion, Formaldehyde ) (eg ruuvitag, govee)
2. added check for properties if not set in device edit

1. added autocreate of BLE sensors type device(temp, humidity, motion, ... ) (eg ruuvitag, govee) when ruuvi beacons gets created these devices are represented as 2 indigo devices one a beacon and the otehr the sensor with this addon the sensor type get created at teh same time when the beacon type gets detected and created.

2. fixed batterylevel for beacons that are also sensor type devices (eg govee, ruuvi,..)

3. added variables for number of sensor devices online/offline (away / home) xx_SENSORS_nAway and _nHome

4. added option in config for individual sensor devices be part of a group1..4 for home/away

added function #3 and #4 enable to see quickly how many sensor devices that are (not) online and total number of sensors

requires indigo 2022.1 or later

1. prep for indigo 2022 and os 12.3
2. added support for CO2 sensor sensirion scd30

1. made BLEconnect a threaded program with priority for switchbot. now response is much faster ~ 1-3 secs
2. most common dev states are now set in plugin and not in devices.xml that will enable in the future dynamic add / remove of states ie pi_16_Signal will be gone if you don't have pi_15 in addition all temperature humidity, Co2, formaldehyde, VOC etc now have common statistic states eg TemperatureChange10Minutes, TemperatureAveToday max / min etc makes it easier to maintain and keep consistent, only one place needed to change for all device types
3. fixed some typos
4. added some debug statements for relays

1. made BLEconnect a threaded program with priority for switchbot. now response is much faster ~ 1-3 secs
2. most common dev states are now set in plugin and not in devices.xml that will enable in the future dynamic add / remove of states ie pi_16_Signal will be gone if you don't have pi_15 in addition all temperature humidity, Co2, formaldehyde, VOC etc now have common statistic states eg TemperatureChange10Minutes, TemperatureAveToday max / min etc makes it easier to maintain and keep consistent, only one place needed to change for all device types
3. fixed some typos

1. made BLEconnect a threaded program with priority for switchbot. now response is much faster ~ 1-3 secs
2. most common dev states are now set in plugin and not in devices.xml that will enable in the future dynamic add / remove of states ie pi_16_Signal will be gone if you don't have pi_15 in addition all temperature humidity, Co2, formaldehyde, VOC etc now have common statistic states eg TemperatureChange10Minutes, TemperatureAveToday max / min etc makes it easier to maintain and keep consitent, only one place needed to change for all device types

made BLEconnect a threaded program with priority for switchbot. now reposne is much faster ~ 1-3 secs

1. added calibration options for sensirion scd30 CO2 sensor
2. fixed switchbot program on RPI
3. fixed output-gpio high / low for inverse/ not inverse config

Added features / changes in v7.138.549@ 2022-02-21

1. added calibration options for sensirion scd30 CO2 sensor
2. fixed switchbot program on RPI

fixed output-gpio high / low for inverse/ not inverse config

added support for sensirion scd30 CO2 sensor and prepartions for python 3

added config option to enabled / disable rpi ip # check set to off if your RPI are in a separate subnet. then the router will replace the rpi ip# with its own

changed setting of local ip number determination: was set by IP # of MAC, now ip numbers of RPi(s) is used (first 2 octet eg 192.168.x.x are used) this is used to block incoming socket connections fro non local ip numbers set option in plugin config

tuned switchbot and hci bluetooth channel management (timing etc) on RPIs

added RPI dev states for hci info, which port used etc

fixed: switchbot setup

fixed: piBeacon Error setting up OUTPUT Line 4821 has error='holdSeconds'

fixed: piBeacon Error setting up OUTPUT Line 4821 has error='holdSeconds'

performance improvements when using 2 bluetooth channels on RPI

1. added support for several switchbot devices

   • temp + humidity, set states: temperature, humidity, battery
   • contact, set states: onoff, last open, short open, long open, light, press count ..
   • motion, set states: onoff, last motion, light, ...

   • curtain, can set mode : slow, fast, and position the device between 0/100 = open closed as an indigo dimmer device a curtain can be operated with an ssh command: ssh pi@ip# echo '{"mac":mac#,"pos":"0...100"}' temp/switchbot.cmd for direct position echo '{"mac":mac#,"pos":"open"}' temp/switchbot.cmd for moving to open echo '{"mac":mac#,"pos":"close"}' temp/switchbot.cmd for moving to close echo '{"mac":mac#,"pos":"pause"}' temp/switchbot.cmd for stopping any move

     • only o c p are needed (not open close pause)

   • bot, can set modes up/down/ inverse, and set on/ off as indigo relay device a bot can be operated with an ssh command: ssh pi@ip# echo '{"mac":mac#,"onOff":"1/0"}' temp/switchbot.cmd

   they all suport battery level states they all benefit from having "brother" devices - the beacons for each type, they expose mac number and battery level.

   These devices all send and receive bluetooth messages. The RPI's will be talking bluetooth with them and send / receive commands/ status from to indigo for the output devices: curtain & bot you need an extra BLE dongle besides the internal

1. switch bot now supports remote commands through ssh (ie iphone short cuts) ssh pi@ ip# password then echo '{"mac#":"xx:xx:xx:xx:xx","onOff":"1"}' > /home/pi/pibeacon/temp/switchbot.cmd

1. added support battery values for all switchbot type beacons and auto population of battery level for switchbot bot relays
2. fixed auto update when new version ships

1. added support for switch bot temperature humidity display / sensor
2. added batterylevel version states for switchbot bot

1. added support for switch bot devices they have to be "associated" to a single RPi in device edit you need to first find the MAC # either through detect new beacons or through iphone app then create switch bot indigo device add mac# and select RPi that is closest to device rest should be left at default then the device will behave like a relay you can set the "hold" time with the iphone app --- these device can be used to eg switch press an apple power button

2. fixed issue with inkbird pool temp sensor

maintenance release - fixed various smaller siuues, mostly for exceptions - small performance improvements

1. some code cleanup for BLEconnect - iphones and BLEconnect-sensors
2. added some debugging logs in plugin
3. fixed error with static / dynamic ip number settings in RPI device edit
   and accept blocking non local ip numbers to connect to the plugin

1. some code cleanup for BLEconnect - iphones and BLEconnect-sensors
2. added some debugging logs in plugin
3. fixed error with static / dynamic ip number settings in RPI device edit

1. added sensor type BLE inkBird Pool 01B ( not R!!) this is the first floating pool temperature sensors that can be read by indigo. The old pool temp sensor RFXcom from scientific was discontinued to install: put batteries into inkbird, put it next to RPI; menu / accept new beacons: select Inkbird After a minute a new beacon device should be created. That is just a regular ibeacon device. Now create a new indigo device "pibeacon / BLE-inkBird.." and copy the mac address from the ibeacon device into teh MAC field Select the RPI that is next to the pool, leave the other parameters as they are (you could set the color of the sensor dot to different values)
2. small bug fixes for special circumstances

fixed label for dev state: particles_100um ( was airquality) in control page and trigger page

added option for airquality sensors to set name for airpolution name in device edit

fixed average rollover at mid night for sensors

fixed error='key groupMember not found in dict' is an issue only for non beacon typ devices

fixed error='key groupMember not found in dict'

added variables for all PI, BLEconnect and beacon devices: # of devices home and away this can be used to trigger is any change in # of devices home/away changes this is in addition to the regular groups: Family, guests, other 1,2 3 this groups can be named as you like in config

1. supports the latest SSD (march 20 2021)
2. added option to block any ip number accessing the indigo mac that does not have the same first 2 octets to avoid ansering outside ip numbers from probing, they will just be ignored, no acknowledge packet is send only works if mac and rpi have the same 2 octets, eg 192.168.x.y and 192,.1678.x.z would be accepted, but not 72.60.4.5
3. fixed group status memebrship for rpis, was ok for beacons

supports the latest SSD (march 20 2021)

1. supports the latest SSD (march 20 2021)
2. added option to block any ip number accessing the indigo mac that does not have the same first 2 octets to avoid ansering outside ip numbers from probing, they will just be ignored, no acknowledge packet is send only works if mac and rpi have the same 2 octets, eg 192.168.x.y and 192,.1678.x.z would be accepted, but not 72.60.4.5

supports the latest SSD (march 20 2021)

1. --- only for experts: added option set IP number of RPI to fixed, set in rpi device edit w/o the you initially set the ip number, but the rpi can chnage it eg switching between ethernet and wifi w this option ON the rpi will always send the fixed IP number IN THE data, although it could use a differnt ip# By enabling this YOU must make sure that the data arriving from the RPI comes from the defined fixed IP# otherwise they will be rejected

2. added menu option to send just new pgm and config files, skipping fonts images etc this will reduce bytes by factor 2 to be send to rpi, fonts and images have not changed for several years now

1. fixed dev state lables
2. added option to start any command from pibeacon this is managed by the pibeacon master.py program it will make sure the program launches,
   and stays up and running if requested

tuned INPUT- pulse plugin part for reset of counters

made compatible with 2021-01-17 SSD card

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu pulse device: reset of pulse / gpio input count was not reset pulse device: calculation of counts/ xx beep beacon action: did not work, menu beep did work fine, one parameter was missing

2. added to pulse/coincidence device maxCountperSecondInLastHour state
   min/max count/min today & yesterday state counts/min*scalefactor state for several more states made the number of digits dynamc in count/xx dev states to have at keast 3 significant numbers shown (that is equivalent to 0.1%) the number of significant digits can be set in dev edit

3. set compress data send to plugin to on if data len > 40kb as default. There seems to be a timeout .. issue with larger data. regular data is < 5Kb, larger data (h ad 128k) only happens for detect new beacons etc compress reduces most data by factor of >7

4. changed detect new beacons to use data aquired anyway with hcidump. so no data collection break during detect new beacons process that is not active for hci- socket data aquisition, as that does not deliver all package types, have to do hcidump do catch that data.

5. added beacon type nut v 45 and 46. the comamnds for battery and beep have changed with the new release. the hardware looks identical

6. fixed negative temperatures for govee sensors

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu pulse device: reset of pulse / gpio input count was not reset pulse device: calculation of counts/ xx beep beacon action: did not work, menu beep did work fine, one parameter was missing

2. added to pulse/coincidence device maxCountperSecondInLastHour state
   min/max count/min today & yesterday state counts/min*scalefactor state for several more states made the number of digits dynamc in count/xx dev states to have at keast 3 significant numbers shown (that is equivalent to 0.1%) the number of significant digits can be set in dev edit

3. set compress data send to plugin to on if data len > 40kb as default. There seems to be a timeout .. issue with larger data. regular data is < 5Kb, larger data (h ad 128k) only happens for detect new beacons etc compress reduces most data by factor of >7

4. changed detect new beacons to use data aquired anyway with hcidump. so no data collection break during detect new beacons process that is not active for hci- socket data aquisition, as that does not deliver all package types, have to do hcidump do catch that data.

5. added beacon type nut v 45 and 46. the comamnds for battery and beep have changed with the new release. the hardware looks identical

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu pulse device: reset of pulse / gpio input count was not reset pulse device: calculation of counts/ xx beep beacon action: did not work, menu beep did work fine, one parameter was missing

2. added to pulse/coincidence device maxCountperSecondInLastHour state
   min/max count/min today & yesterday state counts/min*scalefactor state for several more states made the number of digits dynamc in count/xx dev states to have at keast 3 significant numbers shown (that is equivalent to 0.1%) the number of significant digits can be set in dev edit

3. set compress data send to plugin to on if data len > 40kb as default. There seems to be a timeout .. issue with larger data. regular data is < 5Kb, larger data (h ad 128k) only happens for detect new beacons etc compress reduces most data by factor of >7

4. changed detect new beacons to use data aquired anyway with hcidump. so no data collection break during detect new beacons process that is not active for hci- socket data aquisition, as that does not deliver all package types, have to do hcidump do catch that data.

5. added beacon type nut v 2021. the comamnds for battery and beep have changed with the new release. the hardware looks identical

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu pulse device: reset of pulse / gpio input count was not reset pulse device: calculation of counts/ xx beep beacon action: did not work, menu beep did work fine, one parameter was missing

2. added to pulse/coincidence device maxCountperSecondInLastHour state
   min/max count/min today & yesterday state counts/min*scalefactor state for several more states made the number of digits dynamc in count/xx dev states to have at keast 3 significant numbers shown (that is equivalent to 0.1%) the number of significant digits can be set in dev edit

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu pulse device: reset of pulse / gpio input count was not reset pulse device: calculation of counts/ xx beep beacon action: did not work, menu beep did work fine, one parameter was missing

2. added to pulse/coincidence device maxCountperSecondInLastHour state
   min/max count/min today & yesterday state counts/min*scalefactor state for several more states made the number of digits dynamc in count/xx dev states to have at keast 3 significant numbers shown (that is equivalent to 0.1%)

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu pulse device: reset of pulse / gpio input count was not reset pulse device: calculation of counts/ xx beep beacon action: did not work, menu beep did work fine, one parameter was missing

2. added to pulse/coincidence device maxCountperSecondInLastHour state
   min/max count/min today & yesterday state counts/min*scalefactor state for several more states

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu pulse device: reset of pulse / gpio input count was not reset pulse device: calculation of counts/ xx beep beacon action: did not work, menu beep did work fine, one parameter was missing

2. added: maxCountperSecondInLastHour state for pulse/coincidence device min/max count/min today & yesterday state for pulsepulse/coincidence device counts/min*scalefactor state for pulsepulse/coincidence device

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu
2. fixed: reset of pulse / gpio input count was not reset
3. fixed: calculation of counts/ xx
4. added: maxCountperSecondInLastHour state for pulse/coincidence device min/max count/min today & yesterday state for pulsepulse/coincidence device counts/min*scalefactor state for pulsepulse/coincidence device

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu
2. fixed: reset of pulse / gpio input count was not reset
3. fixed: calculation of counts/ xx
4. added: maxCountperSecondInLastHour state for pulse device min/max count/min today & yesterday state for pulse device counts/min*scalefactor state for pulse device

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu
2. fixed: reset of pulse / gpio input count was not reset
3. fixed: calculation of counts/ xx
4. added: maxCountperSecondInLastHour state for pulse device

1. fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu
2. fixed: reset of pulse / gpio input count was not reset
3. fixed: calculation of counts/ xx

fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu

reset of pulse / gpio input count was not reset

fixed: piBeacon Error Line 6819 has error=list index out of range in confirmdeviceIDINPUTBUTTONmenu

1. added BLE sensors: xiaomi formaldehyde sensor
2. fixed bug that made BLE sensor devices not being active on RPi after comm disable/enable
3. added check if reset for min/max sensor values was already at 0 am - might have been done several times between 0 and 1 am
4. fixed typo for MoistureMinYesterday was MoistureeMinYesterday

1. added BLE sensors: blueradio sensor bug, support temp, light and orientation
2. changed number to float in device states for indigo version 7.5

added BLE sensors: Govee Temp & humidity sensors, they broadcast T, H, BatteryLevel - H5101 w small display - H5075 w medium display - H5177 w large display - H5174 outside sensor, no display

Xiaomi MiJia Bluetooth Xiaomi MiJia MI clock w temp humidity(LYWSD02) w clock temp/hum display 2xcr2032
shows T, H, Batterylevel. and count (message#) in indigo dev states
This sensor sends out Broadcasts w T, H , Battery and count

works similar to Ruuvitag, w display, but no preasure and acceleration info. you need to use the Xiaomi mi home app to setup the sensor (connect to china server, todate that sensor was not supported on servers outside china)

1. added option to use 2 UBS BLE dongles, beta

2. added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

1. added option to use 2 UBS BLE dongles, beta

2. added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

1. added option to use 2 UBS BLE dongles, beta

2. added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

1. added option to use 2 UBS BLE dongles, beta

2. added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

Added features / changes in v7.131.475@ 2020-12-04

1. added option to use 2 UBS BLE dongles, beta

2. added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

1. added option to use 2 UBS BLE dongles, beta

2. added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

1. added option to use 2 UBS BLE dongles, beta

2. added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

added sensors:

Vendor sensorName battery Freqquency Size App Type of Sensor ------------------------------------------------------------------------
Ibeacon On/off or ON Temp ExTemp Hum Press Accell/Grav IR Light GAS CO Smoke

ruuvi opensource sensor w BME280 and LIS2DH22 Acceleration sensor
ruuviTag 1x cr2450 1/1s largeRound ruuvi Y Y Y X,Y,Z

Xiaomi MiJia LYWSDCGQ/01ZM round Temp & humidity sensor. w display 1x AAA 1/1s largeRound YES Y Y

Xiaomi Mi LYWSD03MMC square Temp & humidity sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min small Square YES Y Y

Xiaomi Mi VegTrug / Flower Care sensor, requires 2 BLE dongles w display 1x CR2032 1/2Min YES Y Y Y + Moisture+Conductivity

added Bluetooth Temp / humidity sensor: Xiaomi MiJia round. The round one not sqaure! check eg: https://medium.com/@smarthomespot/my-xiaomi-bluetooth-temperature-humidity-sensor-review-d37b32ab1d0

fixed fillMemberListState error

added some debug statements when master on pi can not find indigo or ip number

1. fixed error memberList not defined
2. change secuence of accepting beacons to aloow ignored beacon to be accepted as sensors eg for ruuviTag beacon: it has a beacon and a sensor device, when beacon device was deleted in indigo the mac# was set to ignore and the the sensor device was not updated.

Added features / changes in v7.128.464 @ 2020-11-03

1. switch bluetooth to no socket if bluez python include fails
2. added support for safedome credit card type beacons, wireless rechargeable
3. changed some menu text, spelling and messages shown

1. fixed accpet new beacons signal

2. added new beacons and sensors: Radius RAD beacons

3. added option to change name of group variables from "other1" to eg bicycles .. and you can jnow have up to 5 groups. the varibales will only be cretaed if a the names are set in config b a group has any members (set in device edit)

1. added BLE Temp& humidity sensor from Kaipule - iSensor
2. fixed pIU error not found

added option to use new wpa_supplicant and inetrfaces file in boot directry at every boot this can be used to setup wifi, dhcp etc files creat a wpa_supplicant (for ssid / passw) and or interfaces(dhcp etc) file(s) in /boot on the rpi SSD

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items

3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors: GAS, CO water, alarm , on sensor: door button remoteKey The on/off states are managed according to the cabailities of the sensors Satech STixx sensors, acceleration, temp, humidity, on/off

4. Normally beacon go "up" as soon as a signal is detect. When they are gone / no signal is received: the RPi does not send any info to the plugin if no signal. Then the plugin will set them to down after xx secs (normally 90) and after another xx secs to expired In "fastDown" mode: after yy secs (>=10) w/o signal the RPi sends a fast down message to the pluginthen teh plugin will set teh beacon to down, If you have more than 2 RPi you can probably go down to 10 secs, better 20 seconds. That means if the beacons leaves the house you will know in ~ 10+3 secs If you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to eg a bike that arrives in a dedicated space and has a good connection to the RPi it shouldd work well

5. minupSigal and mindownSignal: When set to eg up=-60 and down=-80: the beacon will only go up when it is close to the RPI ~ 1 m. but will stay up until it has eg left the room (>10m) with this setting you can decide if a beacon is in a room - that requires an RPI in each room you like to have this feature

6. changed hcidump method added option to restart BLE scanner every 5 minutes, just in case RPi can not keep up fixed so that 2. ble dongle is not needed This method catches all types of messages while the python socket method ignored some of the mesage types ie mfg info which is used to id a beacon / sensor You can select whcih method to use for all RPi in config, or overwrite in RPI device edit.

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items

3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors for GAS, CO water, alarm ... EN61, ES61, EW70, ET90, IM21, IX30 IX32 Satech STixx sensors, acceleration, temp, humidity, on/off

4. Normally beacon go "up" as soon as a signal is detect. When they are gone / no signal is received: the RPi does not send any info to the plugin if no signal. Then the plugin will set them to down after xx secs (normally 90) and after another xx secs to expired In "fastDown" mode: after yy secs (>=10) w/o signal the RPi sends a fast down message to the pluginthen teh plugin will set teh beacon to down, If you have more than 2 RPi you can probably go down to 10 secs, better 20 seconds. That means if the beacons leaves the house you will know in ~ 10+3 secs If you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to eg a bike that arrives in a dedicated space and has a good connection to the RPi it shouldd work well

5. minupSigal and mindownSignal: When set to eg up=-60 and down=-80: the beacon will only go up when it is close to the RPI ~ 1 m. but will stay up until it has eg left the room (>10m) with this setting you can decide if a beacon is in a room - that requires an RPI in each room you like to have this feature

6. changeed hcidump method to include more advertising message types. in v.451 some where excluded added option to restart BLE scanner every 5 minutes, just in case RPi can not keep up fixed so that 2. ble dongle not needed

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items

3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors for GAS, CO water, alarm ... EN61, ES61, EW70, ET90, IM21, IX30 IX32 Satech STixx sensors, acceleration, temp, humidity, on/off

4. Normally beacon go "up" as soon as a signal is detect. When they are gone / no signal is received: the RPi does not send any info to the plugin if no signal. Then the plugin will set them to down after xx secs (normally 90) and after another xx secs to expired In "fastDown" mode: after yy secs (>=10) w/o signal the RPi sends a fast down message to the pluginthen teh plugin will set teh beacon to down, If you have more than 2 RPi you can probably go down to 10 secs, better 20 seconds. That means if the beacons leaves the house you will know in ~ 10+3 secs If you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to eg a bike that arrives in a dedicated space and has a good connection to the RPi it shouldd work well

5. minupSigal and mindownSignal: When set to eg up=-60 and down=-80: the beacon will only go up when it is close to the RPI ~ 1 m. but will stay up until it has eg left the room (>10m) with this setting you can decide if a beacon is in a room - that requires an RPI in each room you like to have this feature

6. changeed hcidump method to include more advertising message types. in v.451 some where excluded added option to restart BLE scanner every 5 minutes, just in case RPi can not keep up

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items

3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors for GAS, CO water, alarm ... EN61, ES61, EW70, ET90, IM21, IX30 IX32 Satech STixx sensors, acceleration, temp, humidity, on/off

4. Normally beacon go "up" as soon as a signal is detect. When they are gone / no signal is received: the RPi does not send any info to the plugin if no signal. Then the plugin will set them to down after xx secs (normally 90) and after another xx secs to expired In "fastDown" mode: after yy secs (>=10) w/o signal the RPi sends a fast down message to the pluginthen teh plugin will set teh beacon to down, If you have more than 2 RPi you can probably go down to 10 secs, better 20 seconds. That means if the beacons leaves the house you will know in ~ 10+3 secs If you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to eg a bike that arrives in a dedicated space and has a good connection to the RPi it shouldd work well

5. minupSigal and mindownSignal: When set to eg up=-60 and down=-80: the beacon will only go up when it is close to the RPI ~ 1 m. but will stay up until it has eg left the room (>10m) with this setting you can decide if a beacon is in a room - that requires an RPI in each room you like to have this feature

6. changeed hcidump method to include more advertising message types. in v.451 some where excluded added option to restart BLE scanner every 5 minutes, just in case RPi can not keep up

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items

3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors for GAS, CO water, alarm ... EN61, ES61, EW70, ET90, IM21, IX30 IX32 Satech STixx sensors, acceleration, temp, humidity, on/off

4. Normally beacon go "up" as soon as a signal is detect. When they are gone / no signal is received: the RPi does not send any info to the plugin if no signal. Then the plugin will set them to down after xx secs (normally 90) and after another xx secs to expired In "fastDown" mode: after yy secs (>=10) w/o signal the RPi sends a fast down message to the pluginthen teh plugin will set teh beacon to down, If you have more than 2 RPi you can probably go down to 10 secs, better 20 seconds. That means if the beacons leaves the house you will know in ~ 10+3 secs If you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to eg a bike that arrives in a dedicated space and has a good connection to the RPi it shouldd work well

5. minupSigal and mindownSignal: When set to eg up=-60 and down=-80: the beacon will only go up when it is close to the RPI ~ 1 m. but will stay up until it has eg left the room (>10m) with this setting you can decide if a beacon is in a room - that requires an RPI in each room you like to have this feature

6. change hcidump method to include more advertising message types. in v.451 some where excluded

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items
3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors for GAS, CO water, alarm ... EN61, ES61, EW70, ET90, IM21, IX30 IX32 Satech STixx sensors, acceleration, temp, humidity, on/off

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items
3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors for GAS, CO water, alarm ... EN61, ES61, EW70, ET90, IM21, IX30 IX32 Satech STixx sensors, acceleration, temp, humidity, on/off

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items

3. In addition to the Ruuvitag added several blue tooth sensors, very easy to setup, they all can be used as presence as well as sensors They have long battery life and > 30 m distance -- with several RPi in the house essetially the whole house is covered INGICS: iBS01-x: Family of on/off sensors- Button, magent, movement, external switch iBS01T: Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03-x: Family of on/off sensors- Button, magent, movement, external switch iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, water proved iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor iSensor - Kaipule various on/off sensors for GAS, CO water, alarm ... EN61, ES61, EW70, ET90, IM21, IX30 IX32 Satech STixx sensors, acceleration, temp, humidity, on/off

4. Normally beacon go "up" as soon as a signal is detect. When they are gone / no signal is received: the RPi does not send any info to the plugin if no signal. Then the plugin will set them to down after xx secs (normally 90) and after another xx secs to expired In "fastDown" mode: after yy secs (>=10) w/o signal the RPi sends a fast down message to the pluginthen teh plugin will set teh beacon to down, If you have more than 2 RPi you can probably go down to 10 secs, better 20 seconds. That means if the beacons leaves the house you will know in ~ 10+3 secs If you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to eg a bike that arrives in a dedicated space and has a good connection to the RPi it shouldd work well

5. minupSigal and mindownSignal: When set to eg up=-60 and down=-80: the beacon will only go up when it is close to the RPI ~ 1 m. but will stay up until it has eg left the room (>10m) with this setting you can decide if a beacon is in a room - that requires an RPI in each room you like to have this feature

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items
3. added several blue tooth sensors, very easy to setup INGICS: iBS01: Has one on/off sensor: either Button, magent, movement, external Switch iBS01T: has Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03: Has on/off sensor: Button or magnet iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe, good for pool etc iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor

4. made "fastDown" work nicely, If you have more than 2 RPi you can probably go down to 10 secs that means if the beacons leaves the house you will know in ~ 10+3 secs if you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to a bike that arrives in a dedicated space and has a good connection to the RPi it shouldd work well

5. added .upper() for hexCode in knownbeacon tags, to make sure that eg aB is seenas AB in the hex string

5

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items
3. added several blue tooth sensors, very easy to setup INGICS: iBS01: Has 3 on/off sensors- Button and magent, movement iBS01T: hase Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03: Has 2 on/off sensors- Button and magent iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor

4. made "fastDown" work nicely, If you have more than 2 RPi you can probably go down to 10 secs that means if the beacons leaves the house you will know in ~ 10+3 secs if you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to a bike that arrives in a dedicated space and has a good connection tot the RPi it shouldd work well

5. added .upper() for hexCode in knownbeacon tags, to make sure that eg aB is seenas AB in the hex string

6. fixed some issues w fast down and BLEconnect

1. cleaned up some code
2. rearanged some menu items, clearer structure, using some color for menu items
3. added several blue tooth sensors, very easy to setup INGICS: iBS01: Has 3 on/off sensors- Button and magent, movement iBS01T: hase Temp and humidity iBS01RG: x-y-z acceleration/ gravity sensor iBS02: PIR presence ir IR object detection iBS03: Has 2 on/off sensors- Button and magent iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor

4. made "fastDown" work nicely, If you have more than 2 RPi you can probably go down to 10 secs that means if the beacons leaves the house you will know in ~ 10+3 secs if you have just one RPI and have it connected to something that moves around in the house it is likely not a good idea but for eg a beacon that is connected to a bike that arrives in a dedicated space and has a good connection tot the RPi it shouldd work well

5. added .upper() for hexCode in knownbeacon tags

1. added .upper() for hexCode in knownbeacon tags

added .upper() for hexCode in knownbeacon tags

1. cleaned up some code
2. rearanged some menu items, clearer structure
3. added several blue tooth sensorss: INGICS: iBS02: PIR presence ir IR object detection iBS03: Has 2 on/off sensors Button and magent iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor

fixed some errors in device edit when fields were not set

1. cleaned up some code
2. rearanged some menu items, clearer structure
3. added several blue tooth sensorss: INGICS: iBS02: PIR presence + IR object detection iBS03: Has 2 on/off sensors- Button + magnet iBS03G: Movement detection of beacon on/off iBS03T: on board temp sensor iBS03TP: on board temp sensor + temp sensor probe iBS03RG: x-y-z acceleration/ gravity sensor Minew E8: x-y-z acceleration/ gravity sensor

Added features / changes in v7.126.438 @ 2020-08-31

1. fixed buffer overflow in new hcidump method

Added features / changes in v7.126.436 @ 2020-08-31

1. added new method (option) to read beacons using hcidump & lescan instead of python socket calls
2. added several "feasy" type beacons w battery level support in std message

1. added new method (option) to read beacons using hcidump & lescan instead of python socket calls
2. added several "feasy" type beacons w battery level support in std message

1. added new method (option) to read beacons using hcidump & lescan instead of python socket calls
2. added several "feasy" type beacons w battery level support in std message

1. added new method (option) to read beacons using hcidump & lescan instead of python socket calls
2. added several "feasy" type beacons w battery level support in std message

1. added new method (option) to read beacons using hcidump & lescan instead of python socket calls
2. added several "feasy" type beacons w battery level support in std message

added several "feasy" type beacons w battery level support in std message

added several "Minew" type beacons w battery level support in std message

1. added menu option to reload known beacon tags (for dev)
2. added some debug statements for get battery
3. fixed known beacon tag for mini beacon, there was a space in the hex number string, (fat finger)

1. rectified difference in beacon .. device type models is allows sensor change, updates.. now fixed at startup
2. can now change battery command in device edit (will only be set to default at first edit device)
3. added check in print battery report and adding special debug for selecting beacons in get battery level

fixed some issues w get battery levels when devices were not properly defined, ...

1. several small fixes, typos, menus ..
2. fixed some properties of ruuvi tag sensor and settings
3. added option in ibeacon device edit to not run get beattery level for individual beacon at 4 am, as eg nutale beacons beep for 5 secs when get beacon runs (they beep when connection to a host is lost)

added sensor bosch BMP388 high precision pressure accurancy equivalent = 0.8m altitude change

for ADSxx ADC devices alsoways show INPUT as ststaus (was INPUT_x)

1. re-wrote get battery level, beep functions, BLE analysis, get new beacon info. also added a beaconloop restart after any of the above functions to avoid a hanging BLE stack
2. fixed battery level calculation for Aiko beacons (it uses a range value:64 = 0% .. value:100 =100 %)
3. added more tagging features for beacons
4. RINEX and NJOII are now the same type of beacon if you have a RINEX or NJOII you need to edit and set beacon type
5. some samller menue changes
6. some smaller program changes

1. rewrote get battery level and peeb functions.
2. added more tagging features for beacons
3. RINEX and NJOII are now the same type of beacon if you have a RINEX or NJOII you need to edit and set beacon type

1. clarified menues for get battery levels for ibeacons normally battery level gets executed 3 times a day, if last update is older than 16 hours for each individula beacon.
2. for new beacosn battery parameters are now automatically set, for existing beacons you need to edit and save beacon device.

1. cosmetic changes for new beacon reports
2. increased data collection time for new beacon report from 15secs to 25 secs.
3. fixed action reboot rpi# through ssh
4. improved speed of car devices status changes
5. improved new beacon report
6. fixed update to states in devcies edit does not work anymore, changed to batch update ie group members was impacted, need to edit and save all devices / beacons if problem

1. cosmetic changes for new beacon reports
2. increased data collection time for new beacon report from 15secs to 25 secs.
3. fixed action reboot rpi# through ssh
4. improved speed of car devices status changes
5. improved new beacon report

Added features / changes in v7.121.406 @ 2020-06-20

1. added compression of data when #bytes > xxbytes (set in config)
2. there was a limnit in # of bytes to be received from RPIs at ~ 30k, was lifted to 120kbytes running beacon scan with very low cutoff RSSI could produced much more data
3. added beacon report for new and existing beacons start from menu and send request to ONE rpi, set RSSI cutoff to accpet all/many/some/ony very close beacons: BLEAnalysis received for beacons with signal (rssi) > -70; from RPI#:11 ================================ existing_Beacons ============================================ ===MAC# DC:0D:30:92:E3:1F -b-feasy-aaa == ; raw data: n_of_MSG_Types : 4 raw data:
4. 043E26020100001FE392300DDC1A0201060303AAFE1116AAFE20000C6F80000005E43F000414A4
5. 043E26020104001FE392300DDC1A0E16F0FF1B020902DC0D3092E31F640A094653435F42503130
6. 043E2A020100001FE392300DDC1E0201061AFF4C000215FDA50693A4E24FB1AFCFC6EB07647825275165C1
7. 043E27020100001FE392300DDC1B0201060303AAFE1316AAFE10D403676F6F2E676C2F50484E5364 mfg_info : FSC_BP104 MSG_in_10Secs : 4.0 beaconType : [u'Feasy_AAA', u'MiniBeacon'] max_rssi : -53 max_TX : 109 pos_of_reverse_MAC_in_UUID : [] pos_of_MAC_in_UUID : [] possible knownTag options: -- use:Feasy_AAA -- use:MiniBeacon

================================ new_Beacons ============================================ ===MAC# FF:FF:C2:28:06:C3 == ; raw data: n_of_MSG_Types : 2 raw data: - 043E1702010000C30628C2FFFF0B0201060302E0FF030954 - 043E1A02010400C30628C2FFFF0E0DFFFFFFC22806C315FB757117 mfg_info : TF MSG_in_10Secs : 5.3 beaconType : [u'', u''] max_rssi : -60 max_TX : 70 pos_of_reverse_MAC_in_UUID : [-1, -1] pos_of_MAC_in_UUID : [-1, 18] possible knownTag options: -- "name_here":{"battCmd":"off","beepCmd":"off","dBm":"-61","prio":1,"pos":12,"posDelta":0,"tag":"0B0201060302"} -- "name_here":{"battCmd":"off","beepCmd":"off","dBm":"-61","prio":1,"pos":12,"posDelta":0,"tag":"0E0DFFMAC#########"}

1. added debug option on RPI do cd pibeacon echo "A4:DA:32:24:5F:6B" > temp/beaconloop.trackmac will create output like for 10 beacon message, it will give you frequence, some raw info and if accepted or rejected START A4:DA:32:24:5F:6B 30:20.899144 logCount: 10 hex: 6B5F2432DAA41E0201061AFF4C00021553706F747950616C5465727261636F6D1ADDD624CACA 0- A4:DA:32:24:5F:6B ; UUID: 53706f747950616c5465727261636f6d ; Maj: 6877 ; Min: 54820 1- A4:DA:32:24:5F:6B ; tag: SpotyPal ; prio: 1 ; uuidMajMin: [u'SpotyPal', u'6877', u'54820'] ; useOnlyPrioMsg: True tag- A4:DA:32:24:5F:6B ; posFound: 32 ; dPos: 0 ; tag: SpotyPal ; 53706F747950616C5465727261636F ; tagString 53706F747950616C5465727261636F 5- A4:DA:32:24:5F:6B ; rejectThisMessage: False ; UUID: SpotyPal 6877 54820 9- A4:DA:32:24:5F:6B ; tagFound True ; UUID: SpotyPal 11- A4:DA:32:24:5F:6B ; added to beaconMSG 99 A4:DA:32:24:5F:6B ; accepted START A4:DA:32:24:5F:6B 30:24.911548 logCount: 9 hex: 6B5F2432DAA41E0201061AFF4C00021553706F747950616C5465727261636F6D1ADDD624CACB 0- A4:DA:32:24:5F:6B ; UUID: 53706f747950616c5465727261636f6d ; Maj: 6877 ; Min: 54820 1- A4:DA:32:24:5F:6B ; tag: SpotyPal ; prio: 1 ; uuidMajMin: [u'SpotyPal', u'6877', u'54820'] ; useOnlyPrioMsg: True tag- A4:DA:32:24:5F:6B ; posFound: 32 ; dPos: 0 ; tag: SpotyPal ; 53706F747950616C5465727261636F ; tagString 53706F747950616C5465727261636F 5- A4:DA:32:24:5F:6B ; rejectThisMessage: False ; UUID: SpotyPal 6877 54820 9- A4:DA:32:24:5F:6B ; tagFound True ; UUID: SpotyPal 11- A4:DA:32:24:5F:6B ; added to beaconMSG 99 A4:DA:32:24:5F:6B ; accepted

full support of many new beacon types w auto detect

1. added some more beacon definitions ie spotyPal and Rinex
2. take dBm value from knownBeaconTags if txPower == 999 == not set can still be overwritten in device edit
3. made beacontype read only: it is either other or a value from known beacon tags
4. fixed spotypal battery type command
5. cleaned up menus
6. fixed distance unit if not meter config read
7. repeat beep msg to beacon if beep time > 10 secs
8. add connect control in pexpect, try 3 times to reconnect if not successful
9. corrected beacon plot positions circle size
10. added spotypal beep function
11. added rinex beep function
12. added option to force beep if beacon is up or not (only in menu)
13. added option to set rpi to perform beep (only in menu), for action it is always closest
14. for cases where the beacon sends different uuid, and one of them is a known tag, use only the tag in props and description, state will still change
15. limit beep commands repetitin, last beep command must have finished for > 20 sec before new one is accepted
16. battery level command parameter data is now a regular dict, not string with "-" separators, easier to read and understand
17. disable position update for 1+minutes after beep or get battery. otherwise the beacon position jumps around as the closet RPi changes.
18. beep beacon now uses other HCI channel (than beaconloop) if available. This will then not required to restart beaconloop after beep
19. config parameters for position plot: multiply symbol size and multiply largecicle size parameters
20. improved timeliness of closets RPI
21. added state for beacons: iBeepable = YES /no, 1. it has to support beep & 2. the last end of beep must be > 50 secs ago
22. fixed UUID tag name for "nonda" was spelled incorrectly "noda"
23. fixed get battery, was screwd up 2 versions ago
24. added battery / beep report
25. added option to accept new beacons of know types eg in config select accpet new beacons of type spotypal and any new becon with tag spotypal will be added
26. added option to allcept "ALL" known beacons, not just one type
27. beacon plot position added option to put symbol text label at center or right side of large circle
28. added tag def for iTrack=njoiii, swiftFinder=zenlife, cube
29. added tag def for innway, can beep
30. added several tags (beacontypes)
31. updates type of beacon property to make it more consistent
32. added an option to accept all message types or only use tag defined message type
33. in beacon position plot, move beacon label to the left if outside the boarder

1. added some more beacon definitions ie spotyPal and Rinex
2. take dBm value from knownBeaconTags if txPower == 999 == not set can still be overwritten in device edit
3. made beacontype read only: it is either other or a value from known beacon tags
4. fixed spotypal battery type command
5. cleaned up menus
6. fixed distance unit if not meter config read
7. repeat beep msg to beacon if beep time > 10 secs
8. add connect control in pexpect, try 3 times to reconnect if not successful
9. corrected beacon plot positions circle size
10. added spotypal beep function
11. added rinex beep function
12. added option to force beep if beacon is up or not (only in menu)
13. added option to set rpi to perform beep (only in menu), for action it is always closest
14. for cases where the beacon sends different uuid, and one of them is a known tag, use only the tag in props and description, state will still change
15. limit beep commands repetitin, last beep command must have finished for > 20 sec before new one is accepted
16. battery level command parameter data is now a regular dict, not string with "-" separators, easier to read and understand
17. disable position update for 1+minutes after beep or get battery. otherwise the beacon position jumps around as the closet RPi changes.
18. beep beacon now uses other HCI channel (than beaconloop) if available. This will then not required to restart beaconloop after beep
19. config parameters for position plot: multiply symbol size and multiply largecicle size parameters
20. improved timeliness of closets RPI
21. added state for beacons: iBeepable = YES /no, 1. it has to support beep & 2. the last end of beep must be > 50 secs ago
22. fixed UUID tag name for "nonda" was spelled incorrectly "noda"
23. fixed get battery, was screwd up 2 versions ago
24. added battery / beep report
25. added option to accept new beacons of know types eg in config select accpet new beacons of type spotypal and any new becon with tag spotypal will be added
26. added option to allcept "ALL" known beacons, not just one type
27. beacon plot position added option to put symbol text label at center or right side of large circle
28. added tag def for iTrack=njoiii, swiftFinder=zenlife, cube
29. added tag def for innway, can beep
30. added several tags (beacontypes)
31. updates type of beacon property to make it more consistent
32. added an option to accept all message types or only use tag defined message type
33. in beacon position plot, move beacon label to the left if outside the boarder

1. added some more beacon definitions ie spotyPal and Rinex
2. take dBm value from knownBeaconTags if txPower == 999 == not set can still be overwritten in device edit
3. made beacontype read only: it is either other of a value from known beacon tags
4. fixed spotypal battery type command
5. cleaned up menus
6. fixed distance unit if not meter config read
7. repeat beep msg to beacon if beep time > 10 secs
8. add connect control in pexpect, try 3 times to reconnect if not successful
9. corrected beacon plot positions circle size
10. added spotypal beep function
11. added rinex beep function
12. added optiuon to force beep if beacon is up or not (only in menu)
13. added optiuon to set rpi to perform beep (only in menu), for action, always closest

. added some more beacon definitions ie spotyPal and Rinex 2. take dBm value from knownBeaconTags if txPower == 999 == not set can still be overwritten in device edit 3. made beacontype read only: it is either other of a value from known beacon tags 4. fixed spotypal battery type command 5. cleaned up menus 6. fixed distance unit if not meter config read 7. repeat beep msg to beacon if beep time > 10 secs 8. add connect control in pexpect, try 3 times to reconnect if not successful 9. corrected beacon plot positions circle size 10. added spotypal beep function

1. added some more beacon definitions ie spotyPal and Rinex
2. take dBm value from knownBeaconTags if txPower == 999 == not set can still be overwritten in device edit
3. made beacontype read only: it is either other of a value from known beacon tags
4. fixed spotypal battery type command
5. cleaned up menus
6. fixed distance unit if not meter config read
7. repeat beep msg to beacon if beep time > 10 secs
8. add connect control in pexpect, try 3 times to reconnect if not successful

1. added some more beacon definitions ie spotyPal and Rinex
2. take dBm value from knownBeaconTags if txPower == 999 == not set can still be overwritten in device edit
3. made beacontype read only: it is either other of a value from known beacon tags
4. fixed spotypal battery type command
5. cleaned up menus
6. fixed distance unit if not meter config read

enabled beacon beep command for specific beacons

added beep function

added free text color settings for device properties

1. added 3 different font sizes for position plot
2. added option to randomize beacon+BLE positions by 0/10/20/30/40%
3. added timestamp to position plot, set in config
4. added delay in master start from getbattery level to ensure that message was send to plugin
5. added RuuviTag sensors they are iBeacons, T,H,P gravity field and movement sensors no setup of the device is needed battery life is > 1 Year, but they are larger than regular iBeacon devices

1. added light sensor MAX44009 This is a very simple fully autoscale light sensor range 0.045 .. 188,000 Lux has 2 i2c address configurable

2. added state: clostestiBeaconLast it inherits from clostestiBeacon when that changes

3. fixed:

4. devices edit for CAR devices, did not list choices for members. My fault, created 3 V ago
5. some typos and menue changes

1. fixed timezone setting
2. added check for install NTP (apt-get install ntp)
3. suppress msg for stopBLE file not fouund
4. changed logging on RPI, date format and logfile now /var/log/pibeacon (no .log)

fixed startup issues

added a delay (min time between probes= 3 secs) in between BLE probes to phone. this is needed for eg pizero when everything goes through one com dev

fixed problem on RPI: get battery level could stopped getting regular ibeacon message

ixed problem on RPI, stack did not restart after boot (a" instead of a ;")

Added features / changes in v7.118.338 @ 2020-02-17

1. added option for several sensor types to have red/grey/green status column colors in devcice edit (for sensors only) you can set the condition when the icon should be red/grey/green eg green: 20<x<30, grey 30<=x<60, red x>=60, where x is the sensor value as shown in the status field

2. fixed action shutdown rpi through ssh command timing issue for some slower RPI network connections

3. now has 20 ibeacon RPi and 20 RPI sensor only RPI. you might need to restart the plugin twice to get all the new states loaded.

4. the ibeacon state Names are now Pi_xx_Signal .. _Distance .._Time = 2 digits for all pi_xx states ie Pi_1 --> Pi_01, to make it sort better. and there are now 20 ibeacon RPIs (0-19) and 20 non iBeacon RPI (for sensors only) 20-39

5. fixed issue with wrong ip number on RPI when switching between Wifi and ethernet

6. upgraded ADC converters, more parameters, models :

   1. apply offset and multiplier to value
   2. if Resistor measurement (one resistor to V+or gd, the measurement resistor to gnd or V+, eg light, thermistor ..) will calculate the proper value of the resistor
   3. if value [min,max] = (INPUT -Min)/Max-Min)
   4. if log; log(value)
   5. if 1/value; value = 1/value
   6. apply offset2 and multiplier2
   7. format formula and add unit any input number can be a simple formula eg 1./255

7. plugin now shows RPI power problems as: none

   0 Under-voltage,

   1 ARM freq capped,

   2 Curr throttled,

   3 Soft temp limit active,

   16 Under-voltage occd since reboot,

   17 Throttling occd since reboot,

   18 ARM freq capped occd since reboot,

   19 Soft temp limit occd

8. RPI will reboot if hciconfig shows DOWN for 2 tests in a row ~ 20 sec apart

9. a new program will be running on the RPI: master.sh It will test every 25 secs if master.py is running, if not it will restart it This is mostly for development as starting master.py from the console and logging out will kill it after some seconds .. the parent process stops and then the childprocess also.

10. fixed reboot action, only reboot menue was working

11. cleanup some code in beaconloop and BLEconnect

12. fixed master.sh bug that caused constant restarts of master.py (from V .334)

13. upgraded ADC converters, more paraemteers, models :

    1. Resistor mesasurement (one resistor to V+, the mreasurment resistor to gnd, eg light, thermistor ..)
    2. value [min,max] = (INPUT -Min)/Max-Min)
    3. lin: (value + offset)* multiplier; log; log(value * offset) *multiplier
    4. format formula and unit any input number can be a simple formula eg 1./255

14. added option for BLEconnect to work thorugh commandline tools (hcitool) instead of python code. it seems that running BLEconnect together with wifi on the internal chips can create timeout > 1 sec. ie for a pi0-W use an extermnal BLE-dongle and send BOTH iBeacon AND BLEconnect to the external BLE dongle, pings are const at ~ 5msec.

Added features / changes in v7.117.334 @ 2019-02-09

1. added menu option to update beacon battery level for a SINGLE beacon, not just all

2. added clostestRPIlast and clostestRPIlast states to RPi, ibeacon and BLEconnect states. it show the previous clostest RPI this is not the second clostsest!!

3. added "nohup" to ssh master start, otehrwise master stops when ssh session ends

4. fixed clostest RPI in BLEconnect, was not alwasy showing correct RPI.

5. added requiremnt that two (RSSI values - lastAverage) in sequence > delta signal to trigger deltat signal change. this remove some noise fluctuations of signals that otherwise would trigger delta_signal > xx state.

6. fixed: Error setting up BLEconnect Line 3636 has error=range() integer end a Error Line 12444 has error=Unknown format code 'd'

7. improved stability reading for adafruit moisture sensor

Added features / changes in v7.117.333 @ 2019-02-09

1. fixed pressure format for pascal units (%.0f instead of %d as value is float) fixed BLEconnect was disabled when switching to 16 RPI fixed pressure and humidity offsets, for some sensors (eg BME280) it was applied twice

2. improved dynamic behavior (fast changinging distance) for ultrasound distance sensor.

3. improved BME680 mamangement, added SensorStatus, AirQualityText

4. option to suppress writing certain high frequency dev/states and variables to SQL logger requires Indigo 7.4.1 or higher this can reduce the cpu load of the SQL logger by > 20%..30% variables: pi_IN_x and b_count and lastChanged states: Pi_xx_Time, TxPowerReceived,UUID,closestRPIText,displayStatus,status,batteryLevelLastUpdate,pktInfo,sensorvalue_ui,updateReason
   these are mostly text fields that do not need to be kept in sql history you need to set and select in plugin config will reduce SQL data for device types: beacon, rpi, rpi-sensor, BLEconnect, sensors

5. changed mbar to mBar in config. You need to reselect the pressure unit in config

6. added Adafruit STEMMA Soil Moisture Sensor and Chirp soil sensor it is configured to give rel moisture 0-100%

7. changed message structure (pi --> indigo) from a list to a dict, for easier reading

8. added state "updateReason" for iBeacons to indicat why it was updated

   • timer = data once a minute (90+ % of times)
   • new beacon
   • fast down
   • fast down back
   • beacon is back
   • delta signal = if you enabled that parameter in beacon device edit

9. can now handle python3.x modules on RPI

1. fixed pressure format for pascal units (%.0f instead of %d as value is float) fixed BLEconnect was disabled when switching to 16 RPI fixed pressure and humidity offsets, for some sensors (eg BME280) it was applied twice

2. improved dynamic behavior (fast changinging distance) for ultrasound distance sensor.

3. improved BME680 mamangement, added SensorStatus, AirQualityText

4. option to suppress writing certain high frequency dev/states and variables to SQL logger requires Indigo 7.4.1 or higher this can reduce the cpu load of the SQL logger by > 20%..30% variables: pi_IN_x and b_count and lastChanged states: Pi_xx_Time, TxPowerReceived,UUID,closestRPIText,displayStatus,status,batteryLevelLastUpdate,pktInfo,sensorvalue_ui,updateReason
   these are mostly text fields that do not need to be kept in sql history you need to set and select in plugin config will reduce SQL data for device types: beacon, rpi, rpi-sensor, BLEconnect, sensors

5. changed mbar to mBar in config. You need to reselect the pressure unit in config

6. added Adafruit STEMMA Soil Moisture Sensor and Chirp soil sensor it is configured to give rel moisture 0-100%

7. changed message structure (pi --> indigo) from a list to a dict, for easier reading

8. added state "updateReason" for iBeacons to indicat why it was updated

   • timer = data once a minute (90+ % of times)
   • new beacon
   • fast down
   • fast down back
   • beacon is back
   • delta signal = if you enabled that parameter in beacon device edit

9. can now handle python3.x modules on RPI

1. ++++ STRUCTURAL CHANGE: ++++

   of ibeacon pi-servers increased from (#0-#9) to (#0-#15) == 10 --> 16 pi-servers

   of sensor pi-servers increased from (#10-#19) to (#16-#40) == 10 --> 25 pi servers

   As a consequence CURRRENT pi- servers #0-#9 should not experience any change. BUT current pi-servers #10-#15 will need to be re-created as pi-servers #16 .. #40 (pick any number) ie sensors-only pi-servers Also all sensors and output devices need to point to the new pi-server numbers (device edit of sensors and outputs) you will see a lot of new indigo sql device tables crated and converted from number to real ++++ STRUCTURAL CHANGE: ++++

2. added support for i2c relay from 52pi for RG11 rain sensor. see device edit for details for relay# to dip-switch mapping

3. removed option to foget ALL history, that removed all definitions for all BLE RPI and recreated them with new indigo ID

4. changed default for restart options, apparently indigo does not like ","" in defaults

5. fixed bug with menu command shutdown rpi

6. many smaller fixed and improvemnst in menus and controls

1. optimized acquisition of battery level for ibeacons

   • repeat process every 8 hours(4/12/20). Request to read if last successfull read was > 17 hour or battery level < 20%
   • send tasks to closest rpi for each beacon
   • prevent up-->down status change for ibeacons during measurement times
   • generate a warning log entry when ibeacon has bad / old info: > 2 days or < 20% once a day at 8am ==> you need to enable this option idividually for each beacon in device edit

2. split of getBeaconParameters.py from execcommands.py to be able to better mange termination of processes

3. added comments in device edit for battery level setting and process.

4. streamlined plugin process to manage do not do up--> donw status changes while RPIs are busy

5. added several comments and explanations to config and device edit

6. added a reboot trigger on RPI if error "too many open files"

1. fixed: get batterly level for noda aiko beacons. they are a little special they use 6 bits, bit 7 is always on, max value is 36 hex = 54 int in device edit you must use the proper ibeacon type for battery value read.

1. device state " batteryLevelLastUpdate" to iBeacon devices. with this information you can see when the last successful update of the iBeacon battery level was obtained.

2. add daily report to indigo log / plugin log if batterylevel to low or update older than 2 days eg: piBeacon Warning batterylevel level test: b-iHere black2 last level reported: 74%, has not been updated for > 2 days: b-iHere_black last level reported: 76%, has not been updated for > 2 days: b-Mazda-aaa level down to: 11% ... charge or replace battery

   if all ok one line "batterylevel level test: no iBeacon found with low battery indicator or old update" is printed to plugin.log you could trigger on event log warning to check for that output

3. if there are any active ibeacons w battery reporting, each morning at 4 or after plugin relaunch the plugin will request a battery level update from the RPIs

added states to sensor devices: eg TemperatureChange10Minutes shows the delta temperature now - 10 minutes ago available for Temperature, humidity, pressure, airquality, CO2, VOC each has 3 states eg 5 minutes/1 hours /12 hours or 10 minutes /1 hour /6 hours .. depending of how which timing makes sense: for co2 and airquaility you want to have fast reaction time (=5 minutes), for temperature and humidity 10 miutes is fine .. In addition you still have min / max today and yesterday

1. improved rd-lidar sensor: option to exclude certain angles from being used in move trigger

2. fix bug: i2c state in RPi, number were wrong for Hex > 20

3. re-wrote the sgp30.py sensor function now does automatic calibration, you can also request a new calibration from menu or an action the sgp30 sensor does sometimes not show in i2cdetect -y 1.

4. added indigo log entry warning:

   piBeacon Warning RPi# 0 has i2c error, not found in i2cdetect sensor: sensor:bme680 - devId:593268732 i2c:119/0x77 <<< when any sensors i2c address is NOT in i2cdetect (excluded is sgp30) you need to edit and save each i2c device to activate

5. added xattr setting for >>pngquant<< png compressing tool (included in the plugin directory used for images (rd-lidar, beacon position). If you select to have no compression selected for images, this tool is not used For it to work you need to have the proper user password set in config.

1. improved rd-lidar sensor:

   • 1. added selection (UBS0...4) or autotdetect of USB port
   • 1. added auto restart when usb gets interrrupted or receonnected
   • 1. added option in rdlidar device edit to select if graph data is send from RPi to indigo. That reduces data by factor of > 10. That data is not needed if no plots are produced.
   • 1. compressed trigger parameter display in graph (list in one line, empty sections now shown)
   • 1. added option to not suppresss values of no measurement in plot. Only meant to show how many gaps in data (angles with no godd quality values)
   • 1. fixed angle display in graph. The sensor spins clock wise while math.sin(phi) goes conter clockwise; the data in display are now also clockwise
   • 1. improved menus w explanations and tooltips.

2. fixed INPUTcount sensor, had one wrong index (integer instead of string for GPIO)

3. Added time stamp to temp/messageSend on RPI. That file contains the last message sedn to the RPI. It is overwritten by the next message. follow it with cd pibeacon <ret> tail -F temp/messageSend <ret> (use -F not -f). lloks linke: 15:15:18 beaconloop: send -- {"msgs":[["24... 15:15:19 rdlidar: send -- {"pi":"0","se...

1. fixed global varibale "currTZ not defined" error on RPI

2. added warning in case /beacon_parameters file becomes too big. also moved that file from temp directory to pibeacon directory as it not written to often.

1. fixed multiple onewire sensor detection

2. improved rd-lidar movement detection and display

added RD lidar sensor, see indigo web site for details

1. small fixes to auto wifi config using file on ssd boot directory

2. small fixes to menus

3. fixes to code on rpi to determine ip numbers etc. ie when in first startup = not connected to indigo

1. added device type 52pi relay i2c HAT. This relay board has 4 relays, set through i2c, you can stack 4 of these boards w 16 total relays, no soldering needed see: wiki.52pi.com/index.php/DockerPi_4_Channel_Relay_SKU:_EP-0099 for details

2. fixed some smaller items, menus etc

3. added option to setup wifi through file on RPI SSD boot directory. this is the directory visible when you mount the SSD on a mac, it should also contain the file config.txt add a file: wifiInfo.json with the exact format: {"SSID":"abc", "passCode":"def"} the file name as well as keys and data are case sensitive. it will add: network={ ssid="abc" psk="def" } to /etc/wpa_supplicant/wpa_supplicant.conf. replace abc and def with your wifi setup.

   the /boot/wifiInfo.json file will be removed once used.

removed a duplicate entry in device edit for RPI fixed ibeacon short message exception fixed network setup when RPI can not ping router

1. switched from ifconfig to ip xx for network info on rpi if os is > 7 (jessie)
2. checking network connectivity now checking for router instead of dns server
3. improved handling of frequencies of sensor updates
4. some smaller menu corrections
5. upgraded neopixel libraries to support rpi4
6. changed DHT temp+humidity sensor to check temp twice and build average (takes ~ 3 secs)

ixed bad plugin prefs error check at startup.

1. fixed situation when plugin deletes RPI, due to MAC number =00:00:00:00:00:00 - bad data coming from RPI

2. tuned IMPULSE sensor

3. made # of digits for sensors consistent

4. added several options for display device on RPI

   • supports xwindows = can show composed (dynamic) images in window on rpi desktop
   • added "thermometer" item to display, w options for labels, ticks etc
   • added zoom factor for xwindows display.
   • it will automatically start xwindows on rpi when indigo output device is an xwindows device type
   • option in rpi device edit to start windows on RPI by rpi-master program

Added features / changes in v7.111.311 @ 2019-09-16

1. debug on rpi now logs individual ibeacon msgs as they come

2. added battery level querry for beacons, shown in dev.states["batteryLevel"] and in detaiuled device listing in indigo main window Prep-steps:::::: you MUST first edit each ibeacon indigo device and set enable battery level .. and select either "randown" or plain com to iBeacons. xy beacons use random, NODA, iHere .. use plain comm. you can try on the rpi with: hciconfig hci0 down hciconfig hci0 up for xy beacons: /usr/bin/gatttool -b MAC# -t random --char-read --uuid=2A19 for iHere, Noda .. /usr/bin/gatttool -b MAC# --char-read --uuid=2A19 replace MAC# with eg 0C:F3:EE:00:66:15 = the mac # of your ibeacon connected to that RPI

    the gatttool will return something like this (or an error message, can not connect)
        handle: 0x002f      value: 64 
       where 64 is the hex value, into integer = 100%
   gatttool will conflict with the regular iBeacon message listening = during that time(..15 secs per ibeacon) no ibeacon messages will be received 
   The RPI that is asked to get the battery level is the "closestRPI" to the iBeacon(see dev.state). When a beacon is not "up" it will not be querried and will keep its battery level unchanged
   

   In order to check if your SSD is supporting gatttol do: ssh pi@... gatttool.. if its says not found you need to upgrade your ssd error messages: -- connect error: software caused connection abort (103) == beaconloop might have restarted and the BLE stack was rebooted, ==> resubmit -- connect error: transport endpoint is not connected (107) == beacon is in state where it rejects requests ==> either ranom on/off or retry -- connect error: function not implemented (38) == beacon is in state where it rejects requests==> either random on/off or retry -- connect error: timeout == connection took longer that 15 seconds, terminated ==> retry

   activate:

   • Set option in ibeacon device edit to enable battery reading
   • A) in pibeacon menu select: "Get iBeacons parameters from rPi" for a one-time update
   • B) create an indigo action group and select "Get iBeacons parameters from rPi ie battery levels" then add a schedule ( eg every 6 hours ) to call that action group.

   This is the first version, some fine tuning will be necessary.