The integration loads, and basic device actions (such as triggering or stopping the tracker sound/chime) work without issues. Furthermore, the Python script used to generate the credentials/secrets executes successfully and without any errors.
However, location data/sensors remain unavailable because the FCM push receiver fails to start, resulting in a missing FCM token during manual or automatic location updates.
Log Output
Logger: custom_components.googlefindmy.Auth.fcm_receiver_ha
Quelle: custom_components/googlefindmy/Auth/fcm_receiver_ha.py:4284
Integration: Google Find My Device
[entry=~~TOKEN DELETED~~] FCM client not in STARTED state after 22.0s; aborting manual locate registration (fail-closed)
Logger: custom_components.googlefindmy.NovaApi.ExecuteAction.LocateTracker.location_request
Quelle: custom_components/googlefindmy/NovaApi/ExecuteAction/LocateTracker/location_request.py:726
Integration: Google Find My Device
Manual locate skipped: no FCM token available (see the preceding warning for the specific cause)
Logger: custom_components.googlefindmy.coordinator.polling
Quelle: custom_components/googlefindmy/coordinator/polling.py:1659
Integration: Google Find My Device
Starting poll cycle without push transport; continuing in degraded mode.
Logger: custom_components.googlefindmy.coordinator.polling
Quelle: custom_components/googlefindmy/coordinator/polling.py:1490
Integration: Google Find My Device
Push transport unavailable for 15s; forcing poll cycle.
The integration loads, and basic device actions (such as triggering or stopping the tracker sound/chime) work without issues. Furthermore, the Python script used to generate the credentials/secrets executes successfully and without any errors.
However, location data/sensors remain unavailable because the FCM push receiver fails to start, resulting in a missing FCM token during manual or automatic location updates.
Log Output