Core: Logbook Presence status spam after updating to 0.106

[MuppetOwl]

The problem

After updating to Home Assistant 0.106 the logbook is spammed with presence status updates. Like at work or at home multiple times even if status is not changed since last time.

• Home Assistant release with the issue:
  0.106.0
  Last working Home Assistant release (if known):
  0.105
• Operating environment (Hass.io/Docker/Windows/etc.):
  hass.io
• Integration causing this issue:
  Presence/Android App

[reaper7]

I confirm observation

[nmacy]

Also receiving the same issue after upgrade to 0.106 on hass.io.

[probot-home-assistant[bot]]

Hey there @robbiet480, mind taking a look at this issue as its been labeled with a integration (mobile_app) you are listed as a codeowner for? Thanks!

[temesinko]

I can confirm this too 👍

[axlthorell]

I have the same issue but not only from the mobile_app integration. I also get spammed with location updates from the tesla integration reporting location tracker updates a couple times a minute.

[crkochan]

I’m experiencing this issue more-so with the location tracker from the Tesla integration than with the mobile_app integration, although it too is showing multiple updates.

In the case of the Tesla integration, I am seeing location updates logged every 15 seconds, +/- a couple seconds.

For mobile updates, they are only happening a few times an hour, but are not happening as a result of transitioning into or out of a zone. So multiple duplicate "\

I am an iOS user running the Home Assistant Companion app, version 2.0.0(69).

• Home Assistant release with the issue:
  0.106.0
• Last working Home Assistant release (if known):
  0.105.5
• Operating environment (Hass.io/Docker/Windows/etc.):
  Home Assistant (hass.io) / Home Assistant Core
• Integration causing this issue:
  
  
  
  • Presence/iOS App (version 2.0.0(69) / 2019.1)
  
  
  • Tesla
  
  

[gadgetchnnel]

Although that PR looks like it will remove these duplicates from the logbook, it doesn't look like these are actually down to the attributes changing.

Querying the database, I have a very large number of device_tracker entries (from the mobile_app integration) which have the same state and attributes with only last_changed and last_updated being different.

The mobile_app WiFi connection sensor may also be doing the same - I don't have this included in my recorder config, but I have an automation which is triggered by this sensor and this was repeatedly firing with no change in WiFi connection state.