So I did a bit more digging and I realized I couldn’t execute the apt -get commands and others in terminal because I’m running Hassio (the one with all the extra addons) with MQTT using Mosquitto broker instead of HA on docker. Is that neccessary to make this work? I find that trying to run these scripts directly just results in a load of errors without any output.
I have enabled bluetooth tracking via this command:
It finds a lot of bluetooth devices and under one of the entities it lists device.tracker.pi_man_sam however it’s listed under “mobile app” and that doesn’t show me any bluetooth options for some reason. I’m not sure if I can just go ahead and use that device tracker for my automations?
Thanks a lot for taking the time! this has already brought me a few steps closer to understanding what I need to do.
The bluetooth tracker is fine, if you don’t mind that you’re going to see every Bluetooth device that ever passes your house. Unless you live in a fairly isolated location, do expect to gain many hundreds, if not thousands, of device_tracker entities as a result. That’s why many of us use monitor
#install git
cd ~
sudo apt-get install git
#clone this repo
git clone git://github.com/andrewjfreyer/monitor
#enter `monitor` directory
cd monitor/
#(optional) switch to beta branch for latest updates and features (may be unstable)
git checkout beta
Thats why I’m asking for more info. Do I need a full mosquito install on Ubuntu as well as the add-on inside my HA, or in place of it? The instructions assume a stand-alone Pi install.
If I put random garbage in it and check config it fails, so I know the file is being parsed.
I’m expecting to have two entity as defined above with a name like device_tracker.pixel_2_xl_bt_tracker and I don’t… neither one gets created. No errors in the homeassistant.log.
What does „hcitool dev“ report?
Maybe you have to power up the Bluetooth device manually.
Launch bluetoothclt and issue „agent on“ and „power on“ commands.
I have the same problem as msbc.
Running it with debian buster and backported kernel 5.8.
(Backported Kernel because i have an intel ax200 wifi card with bluetooth on it that needs a newer kernel than 4.x)
Monitor only prints the cycling hci0 messages. hcitool dev reports hci0 34:C9:3D:BE… and bluetoothctl ‘scan on’ finds my phone and various bluetooth devices in the house.
Any idea where i can look any further?
Edit:
If the monitor.service runs, bluetoothctl shows:
Sorry if I’m blind or something, but are different monitor flags (sudo bash monitor.sh -h) documented somewhere or should I always log to my Pi to read the documentation?
I’ve got some questions regarding how the monitor works. Here’s some background info of my setup:
1x RPi Zero outside where I enter the house.
2x RPi (3B+ & Zero) inside the house
I’m monitoring one ibeacon in my keyring and my IPhone. When I arrive, outside monitor node will pick up my phone and my keys. When inside, keys are usually detected by both inside nodes, but my phone sometimes only by one node. Outside node will detect both my keys and phone occasionally when I’m inside.
Could someone explain what is happening in my current setup when I go inside. Are the nodes communicating to each other so that the outside node knows I’m home based on the nodes inside? So that the outside node is not starting to search for me when it detects random BT signal e.g. from neighbor and I’m not detected outside anymore?
Without sending any manual DEPART messages, when does my monitor detect I’m not home anymore (keys and Iphone not home)? If I’d be to hasty sending the depart-scan and I’d still be in the BT coverage, when would the next depart scan take place? I’m thinking does it make any difference to delay depart-scan for 1-2 minutes after front door opens, or should I just trust the system to detect my absence at its own pace.
This project has already improved my coming-home-presence by a ton, thank you so much for it!
I recently got a new router and have a new network SSID and password. Is there anyway i can change the WIFI credentials on the Pi Zero (Monitor.sh) that I have. I would prefer not to start from scratch again.
I thought i would edit the wpa_supplicant but I cant find it.