High load from iBeacon uuid sensor on database

[Ernst79]

As reported on the forum, the iBeacon is still giving a high load on the database. See https://community.home-assistant.io/t/passive-ble-monitor-integration/303583/361?u=ernst

In this issue, I try to reproduce this behavior and make some notes.

Step 1. Deleted the Database to start with a new fresh empty DB
Step 2. Restarted HA, running a database scan once per 10 minutes.
Step 3. After 20 minutes I have the following number of number of state updates. Seems to be the uuid sensor only.

Step 4. After 30 minutes, uuid has increased with 500 state updates, temperature and humidity only with 9 (one per minute, so 9-10 is as expected).

Step 5. After 40 minutes, uuid has increased with 650 state updates, temperature and humidity only with 10 (one per minute, so 9-10 is as expected).

Step 5. Checked the states, of MAC, major and minor, these had a state change 38 minutes ago, uuid has had a state update 4 seconds ago.

Conclusion
uuid sensor state is updated on every advertisement, while it should change on a change of the uuid (@dmamontov just copying you in, to let you know, I will also have a look myself to see if I can find out why).

[dmamontov]

So I checked now. uuid is written only once at startup. measured power as expected, the average is calculated.

Maybe it's another apple device? which for some reason changes the uuid, and according to the statistics from the screenshots it is clear that the uuid is changing and not the mac.

[Ernst79]

The strange thing is that I don't see any change of the uuid sensor (both the state and all attributes stay the same). It has been the same for hours. But the last update is constantly saying a few seconds ago.

I'm not sure what device it is, could be an apple device, yes. I'll do some further research

[dmamontov]

I have one suspicion. Now I'll do some debugging.

[dmamontov]

Found. I'll send you a PR now.

[dmamontov]

#688

[Ernst79]

Excellent, I also found that the uuid key didn't follow the if statement., but hadn't started solving it. Great, I'll do a final test tonight and will release it tonight.

[Ernst79]

Fixed in 7.5.0