Getting access denied on that link. Also on the new monitor thread the script link doesn’t seem to work for me, at least on my iPhone.
1 Like
Weird markdown errors. I think.
1 Like
Already have access 
to the link.
I have a NOOB question:
how do really trigger the scan for the -t option?
I have three pies and like you @andrewjfreyer One covers all the doors and each have sensors that already communicates with my mqtt server on HA.
Now i have to send the mqtt [topic_path]/scan/depart to the pie running the monitor, to trigger the scan, however i only have HA mqtt, and this should be done on the pie running the monitor, so i’m not sure how to do this part 
1 Like
Can anyone advise if this is a normal scan pattern for an iPhone vs an iTag? I’m worried that my MQTT server (on HASS) might be getting spammed. If it’s normal, that’s fine…
1 Like
Yes, this is normal since the presence of phones is affirmatively determined by scanning but the presence of beacons is inferred based on the last time that a beacon advertised its presence. I’m working on a few techniques to smooth out the beacon confidence reporting, but in the interim you can try changing preference is to include longer delays.
Monitor thread here.
To clarify, are all of your nodes using -t? If one or more of them are not using that argument, those nodes will send that message for you.
Otherwise, in Home Assistant you can post an MQTT notification.
Monitor thread here.
So Far I have no node on the -t option since i didn’t knew how to make them work.
So my “main” pi that report to [topic_path]/sala/mac will report in something that my other pies ([topic_path]/quarto/mac and [topic_path]/garagem/mac) will understand that shell start monitoring?
The -t flag causes the monitor script to only respond to trigger messages. The script, by default, will respond to mqtt messages posted to that topic.
Note, that the “[topic path]” string in the example and documentation is merely a placeholder reference for the mqtt_topicpath variable you have defined in your mqtt_preferences file. So, if you are using default settings and you want to trigger a scan at your notes, the topic path would be: monitor/scan/arrive or monitor/scan/depart
By default, all of your nodes will respond to either of those messages. If you do not want a node to respond to a particular message, include that node’s mqtt_publisher_identity in the message. So, with default settings, omitting the “first floor” node from the scan, the topic path would be: monitor/scan/arrive or monitor/scan/depart and the message would be {"data" : "first floor"}. Sending this message will cause only the “second floor” and the “third floor” to scan; the first floor will ignore the message.
Note the more detailed description of monitor here.
Does anyone know what setting to use for the iTags? Are they beacons or ibeacons? At one point (before I did the Git Pull to add the missing support directory, bizarrely!) Monitor was really responsive to the iTags but now (I’m using -g and the latest version of monitor, with the MAC addresses in the known_beacons file) it’s taking sort of 3-8 minutes for any changes to be noticed and the granular tracking every minute seems to have gone. Monitor still super quick for our iPhones. Thanks
EDIT: Should point out that doing an depart/arrive MQTT publish dramatically helps…
1 Like
iTags are generic beacons and it is not required to include them in the known_beacons file because they report their address publicly.
OK, I’ll try removing them from the known_beacons file - I’m hoping doing so will speed up their recognition - my iPhone is detected within what seems like milliseconds but the iTag seems to take about five minutes before its recognised. Thanks, Andrew, for your patience with this noob! 
1 Like
@andrewjfreyer Just a question on your node flow - probably a dumb one most of this is new to me.
" On the other hand, if the input boolean is false, I set the input boolean to false only if an exterior door on the main floor (including the garage lift) has been opened or closed in the last 10 minutes. This is a final check against false exit events."
How are you updating the boolean for last ten minutes - i can set it based on the state change of door sensor but I couldn’t figure out the best way to update it so it isn’t always on.
Any of you guys using ?
monitor -e report bluetooth environment periodically via mqtt at topic:
[topic path]/environment
If so it would be really helpful if you could share that part of your config if you have a mo so I can wrap my head around how it would help. I’m restarting my instance of HASS pretty often at the moment and I’m finding that obviously when HASS restarts it doesn’t know the presence status of my tracked devices and it takes a state change to correct itself. Rebooting the Pi Zero W is a bit of a blunt tool and doesn’t provide a speedy update, either. Thinking this might help. Thanks!
Whenever I am having that issue I would just use the -a option
monitor -a report all scan results, not just changes
If you do this it should give continually update the results.
@andrewjfreyer - This looks great, many thanks for sharing 
Is there any specific requirement on the bluetooth for the ‘server’ side, other than linux support ? (ie. particular protocol support etc?)
I’d like to get a USB Bluetooth dongle to use from my server instead of a RaspberryPi, I was thinking something like:-
or
https://www.ebay.co.uk/itm/USB-Bluetooth-2-0-EDR-Dongle-Wireless-PC-Adapter-Coverage-up-to-100M-for-Desktop/111931931115?hash=item1a0fa9b9eb:g:dBQAAOSwxp9W4cfv
But I notice they don’t support newer bluetooth protocols like 4.0 etc… is this a problem for the intended purpose? (ie. I don’t actually want to connect to the end device, just detect it’s presence)
I picked those as they have a long advertised range, so would probably be fine using one device in my intended location…
1 Like
As far as it helps…
I have a few of these and use them on older Pi’s which I use for ‘monitor’ and they work fine with current version of ‘monitor’.
1 Like
Sorry, I am new with HA and not programer. Will like to use this with BLE tags for tracking kids (when they come from school to send notification - notify.ios…)
This device_tracker is in fact virtual? And this is then presented in HA as icon with picture with changing status (home,away) with mqtt topic?
Thanx
You’ll want bluetooth 4.0 support to interact with LE devices.
Have you tried linking your state input_booleans to HA’s recorder?
Hi!
Have not installed yet and am new to this. A perhaps simple question. Can this be done? We only have two Android phones to keep track. I have a Yale zwave lock on the only door. Can I set this up so when the lock is opened a arrive scan is started. And when the door sensor is triggered a departscan is triggered.