Device Tracker on Mobile app stopped working with 2024.01

[AlexW75]

The problem

The device tracker of one of my phones stopped working with the update 2024.01.
I have no access to the sensor data of the phone.

According to the log there seems to be a problem with the cloud hooks.
I already updated the home assistant app and did several restarts on the server and devices.

What version of Home Assistant Core has the issue?

2024.01

What was the last working version of Home Assistant Core?

2023.04

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Device Tracker iPhone

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 00:03:26 (1 occurrences)
Last logged: 00:03:26

Error setting up entry iPhoneAlex (14) for mobile_app
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/mobile_app/__init__.py", line 125, in async_setup_entry
    await create_cloud_hook()
  File "/usr/src/homeassistant/homeassistant/components/mobile_app/__init__.py", line 108, in create_cloud_hook
    hook = await cloud.async_create_cloudhook(hass, webhook_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/cloud/__init__.py", line 189, in async_create_cloudhook
    hook = await cloud.cloudhooks.async_create(webhook_id, True)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hass_nabucasa/cloudhooks.py", line 40, in async_create
    raise ValueError("Hook is already enabled for the cloud.")
ValueError: Hook is already enabled for the cloud.

Logger: homeassistant.config_entries
Source: config_entries.py:406
First occurred: 00:04:31 (1 occurrences)
Last logged: 00:04:31

Error setting up entry iPhoneAlex (14) for mobile_app
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 406, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/mobile_app/__init__.py", line 104, in async_setup_entry
    webhook_register(hass, DOMAIN, registration_name, webhook_id, handle_webhook)
  File "/usr/src/homeassistant/homeassistant/components/webhook/__init__.py", line 53, in async_register
    raise ValueError("Handler is already defined!")
ValueError: Handler is already defined!

Additional information

No response

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (mobile_app) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of mobile_app can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign mobile_app Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

mobile_app documentation
mobile_app source
_{^{(message by IssueLinks)}}

[mtibbett67]

Having same issue on Android for 3 devices.

[MartinHjelmare]

The mobile app integration isn't mobile phone brand specific so there's no need to comment with what brand of mobile phone you're using.

We'll ask for more information if we need it. Thank you!

[edenhaus]

It doesn't help to comment the same log entry as in the description again. We are analyzing the problem.
Also Martin has already written, that you don't need to comment each model.

[craigwitter]

Just to add a data point - I have a Pixel 8 running the latest build of Android, and am on 2024.1. My phone is connecting via the Nabu Cloud fine, reporting location and charging data normally.

[Mutley247365]

I'm having the same issue with mobile devices too,
6 devices
1x s22 ultra (still working)
1x tab s8 (still working)
1x other android phone (still working)

1x tab a7 (failed to set up)
1x iPhone (failed to set up)
1x android watch (failed for set up))

All devices were running fine before the update.
I have attempted to reload each device, but there has been no change.

[DrMigbio]

Just to add a data point, not issues with iphone 11 (Firmware: 17.1.2), same problem on iphone 8 16.7.2.

[tislar]

Hey guys I had same issue on all my devices. Solved by loging out from account in app. When logged in again it came back up with same entities!

[dai80027]

I'm going to sound like a real idiot here, but which account did you log out of, in which app, and on which device? Thanks!

[Mutley247365]

Hey guys I had same issue on all my devices. Solved by loging out from account in app. When logged in again it came back up with same entities!

This seamed to work for me.

[WizGnome]

I'm going to sound like a real idiot here, but which account did you log out of, in which app, and on which device? Thanks!

I clicked on my user avatar in the sidebar, scrolled down until the red logout text appeared about halfway down and clicked it. The app then let me login again.

[MrRonnieJ]

Hey guys I had same issue on all my devices. Solved by loging out from account in app. When logged in again it came back up with same entities!

This seamed to work for me.

This worked for me also.

[dai80027]

Logging out of mobile app on each phone worked for me too. Thanks!

[tislar]

Yes it was pure luck. I was messing with old phone and noticed that it came on. Glad to help!

[AlexW75]

Worked for me too logout and than in worked.

[Fontie1]

Worked for me also. Thanks

[edenhaus]

To give more context on the problem and why it happens only to a few devices:

• All mobile app setups after you enabled the Nabucasa cloud are working correctly; therefore, removing and reading the mobile app will work as a workaround.
• If you have set up the mobile app before enabling the cloud, there is a small possibility that you encounter this bug. So, some devices might work and others not.

The best at the end: A fix is inbound and will be part of the 2024.1.1, which will be released today.

[tislar]

To give more context on the problem and why it happens only to a few devices:

• All mobile app setups after you enabled the Nabucasa cloud are working correctly; therefore, removing and reading the mobile app will work as a workaround.
• If you have set up the mobile app before enabling the cloud, there is a small possibility that you encounter this bug. So, some devices might work and others not.

The best at the end: A fix is inbound and will be part of the 2024.1.1, which will be released today.

In my case mobile app was working with cloud for a year now. And all devices had same problem (samsung tablet, xiaomi phone and wifes iphone). Issue was resolved with loging back in. Maybe there is some other thing that is going on?