I can also confirm that enabling active scan in the old integration does fix the updates on the new integration.
By enabling active scan it also shows up the other values (voltage, battery etc).
I can also confirm that enabling active scan in the old integration does fix the updates on the new integration.
By enabling active scan it also shows up the other values (voltage, battery etc).
Does this mean that by using Active Scan (in the new integration), we can expect to see faster battery drain? One of the key benefits of the BLE monitor integration was itās passive scan.
Has anyone found a way to see the mac addresses of the discovered devices? I have 10+ plant monitors and they all show up as Flower Care. Itās impossible to know which one is which.
In the screenshot below, the devices with the mac addresses are temp/humidity monitor devices.
Its on the todo list already,
Workaround, hold your hand on it and check which one increases in temperature.
The workaround I used was to put my hand on the illuminance sensor. This should change immediately the sensor reading.
I put sensor by sensor in a glas of water. Many waysā¦
Would be interested in this as well. For what I understand, active scan means, HA scans for the advertisements, not polling the device. But I might be totally wrong here.
Yes, it will increase battery consumption slightly, but not that much. I thought they had raised an issue for bleak, to allow passive scanning in the core integrations, but dont know the status of that.
I think Iāll hold off updating Core and OS for a couple of cycles as BLE working is vital for my setup - too much depends on it
I (and a few others) are running both in parallel and theyāre working fine (so long as Active Scan is enabled in this integration).
The new integration is clearly a 1.0 and isnāt nearly as far along as this component, but then itās an initial release. Given that Ernst is assisting with the official release, I have no doubt that itāll eventually achieve feature parity.
My only issues are:
Itās worth updating (with a backup) just to see what is and isnāt working for you.
No, itās never worth ājust updatingā - I donāt have the time to fix all the broken stuff. I usually wait until just before a new release but I was away at the end of July.
I think all the above issues will be solved in a future release, but it is indeed a 1.0 version that will be improved over time.
Itās not meant for you to fix stuff, but if you have problems with one thing, you should consider, if the advantages of a new version (regarding everything in that release) outweight the problems of other stuff. Sooner or later you will have to update, because other dependencies will likely stopping to work, if they arenāt updated.
Iām not saying you should upgrade in this case, but you should consider the advantages (and disadvantages) for your setup if you donāt upgrade.
But for this case it doesnāt matter at all: if you upgrade the core and donāt enable the new BT integration in core (assuming you havenāt enabled default_config
), you donāt have to worry, all stays the same. You will still use this integration here and not the native HA one. My suggestion here would be, stay with your usual upgrade rhythm and just donāt enable the new, native BT integration. That should keep you safe with the core, and you can still wait for everything else to be integrated without missing out on new versions. Who knows when specific devices will be implementedā¦
Yes and I usually do (but not until the last release of the cycle as that is the most pain free method) as leaving upgrading can introduce other issues.
However, I am very dependent on the BLE stuff working and donāt have the time to sort issues out right now.
So Iām in a 'aināt broke; donāt fix" mode currently.
There is nothing in the recent releases I need, so happy to bide my time and wait for it to be more stable.
In the future will there be a good way to identify if the sensors I am using now in BLE Monitor are supported by the core integration (ie ATC and ThermoPlus)?
Passive scanning support has been added in v0.15.0
They are working on making individual devices better recognizable, by adding the Mac address to the device info, but that will most likely be in the release next month.
Is anyone else having the issue whereby the new integration only scans for a few minutes after every reboot? Iām wondering if this is caused by running the Passive BLE monitor integration at the same time.
Try to enable active scan in BLE monitor. Several users have reported that this helped.
Ah, sorry, I see you already have this enabled. Could you try and see if it continuous to work when ble monitor is disabled/removed?
Thanks, I think that might be the next step. I have a rather exotic dongle (stop sniggering), so it may also be that.
Disabling this Passive BLE monitor integration does seem to have solved the problem. Unfortunately Iām still relying on this until the new one achieves a closer feature parity, so I may need to disable the new one for now.
I do have another dongle that I can add and give them exclusive use. Hopefully that will work.