In researching, and personal testing, I found the random mac is an issue with iphones, not Android (I only have Android phones), so Iām hoping this will work for me.
Iām struggling to find an Android beacon app that works with this, can anyone make any recommendations?
However, I found that not using any phone beacon app, I can get 2 Android phones to report their rssi values several times (even after reboots, etc), but ONLY while the phone is in pair mode (making itself discoverable I believe). Is this expected? Restarting the phone and turning the bluetooth on and off does NOT trigger any rssi events to openhab (but again, putting the phone is pair mode then gets rssi events to show up in openhab for a couple minues). Iām not quite sure if this is a configuration issue on my end, my 2 phones, the Bluetooth Binding, or openhab itself (or a beacon app is required).
BTW Iām using openhab logs to troubleshoot this and determine the rssi events.
Would your latest fix address any of this by any chance?
To do the update, where do we put the jars (pi 4/raspbian/Debian)? And do we first need to uninstall anything?
Iāve been playing around with āBeacon Simulatorā for Android. It allows you to create simulated advertising beacons such as ibeacon, eddystone, & altbeacon. I tried creating several but nothing is recognized in PaperUi via a search in the inbox. The are a lot of seeing for these beacons tho that I donāt understand. Is this expected or should these be showing up? Iām testing it this way because if this does show up & work with openhab then I could potentially use this as a beacon on my phone to do the presence detection. Thanks!
UPDATE: Just reporting that BlueZ version 5.43 & 5.50 works with this. (ie, sudo apt-get update & sudo apt-get upgrade will not break this if going to 5.50)
I actually just started working on this the other day. But since Iām also juggling quite a few other bluetooth features that will be added in the next release Iām only making a few hours of progress here and there.
But the newest features likely to be included in the next release:
a new bluez binding that doesnāt require tinyb.
roaming device support which would allow a device to report the adapter nearest to it.
another bluetooth device binding for the daikin madoka thermostat.
a binding that allows bluetooth devices exposed over mqtt to be handled by the bluetooth binding framework (which would allow existing bluetooth bindings to handle devices over mqtt)
@hairdresser has been doing a fantastic job in implementing some of these features. He is responsible for creating the new bluez binding, the daikin binding, and the mqtt adapter support.
Iāll try to get the gatt feature done for next release but I canāt guarantee that it will be completed in time since it is a feature that requires significant testing. It also doesnāt help that I donāt have very many devices to test with.
To pursue on this - I can say that I am using those binding for several weeks now, and Iām delighted with stability and performances. Nothing comparable with the previous TinyB that I was never satisfied with.
For BLE devices testing, I suggest you use Bleno, a Node framework to emulate a BLE device. It is a bit tricky to make it work the first time, but if you need any help, and a dummy device to test (my Daikin Madoka emulator), Iām happy to help.
On the iPhone, there is also the LightBlue app which I used as well to emulate a device.
Iām also thinking of a new feature for the Bluetooth binding through DBUS: a custom agent to allow the pairing directly from the binding. Iāve checked the tech details - I just need some time to implement this.
Hello.I am tested this.
I get data from a temperature and humidity sensor using the third-party C ++ + Bluez program on my OrangePi PC + usb dongle bluetooth 4.0. I removed the standard bluetooth binding and installed (in addons folder) first org.openhab.binding.bluetooth.bluez-2.5.4-SNAPSHOT.jar but I did not get the Bluetooth Roaming Controller.
Next, I removed this and downloaded org.openhab.binding.bluetooth-2.5.4-SNAPSHOT.jar and the Bluetooth Roaming Controller showed up in Inbox and was added. But my Xiaomi temperature sensor was never found in Inbox.
Previous topic with my questions (no solved): Xiaomi Mija Sensor Tempetature, Bluetooth (console data)
Iām still not able to cover presence functionality with official binding - anyone has it? @cpmeister - if you have ability to cover this functionality, you would be able probably to become new maintainer of project: 3rd Party Bluetooth Binding. Beta testers needed @vkolotov had to stop it and is lookinf for someone to replace. Itās a great bindig with a lot of functionalities in comparison to official one. A lot of beacons already covered and many adapters can be used. Now, itās not adapted to new openhab version and has some issues with connection - desperately needs new maintainer
Hi, guys any update? I have managed to update bluez to the latest 5.5 version and managed to get bluez bridge online, discovered sensor, but got only RSSI data, no humidity, no temperature data. How to add those channels?
I have good news, I just got roaming device support added into the official bluetooth binding. This feature essentially allows devices to be tracked based on the adapter they are closest to. This is essential for implementing multi-room presence detection.
In other news Iāve almost completed work on GATT channel support for the official bluetooth binding. This feature wonāt be able to make it into the 2.5.9 release but it will definitely make it for the OH 3 release.
Once I have the feature in testable shape Iāll post the jar so everyone can get a go at it.
Also one vote for the Xiaomi Mijia temperature and humidity sensor from me. I am using several ones still with the 3rd party Bluetooth Binding. I could also offer to send you one sensor for testing if this helps.
