icloud3 icon indicating copy to clipboard operation
icloud3 copied to clipboard
verified publisher icon gcobb321

Sensor entities not created

Open Vladx71 opened this issue 4 months ago • 19 comments

Hi,

Recently I had a very strange issue. After configuring the integration everything is fine, however majority of the sensor entities are not created. Originally for one device (Szifonvv) all the sensors are created, but now they disappeared.... for other devices no sensors created. I don't see any issues in the log

Any thoughts why this happening and how to fix it? Family sharing is enabled with my account. I already tried complete removal and adding again the integration. I also installed latest dev version, but the behavior is the same with this and with the stable version.

Screenshot from yesterday

Image

Screenshot from today

Image

Vladx71 avatar Aug 25 '25 08:08 Vladx71

  1. The sensors created are different for tracked devices (iphones, watches, ipads) and monitored devices (AirPods?).
  2. Review the sensors displayed on the iCloud3 Dashboard screens. You will need to recreate the dashboard screen after added new devices.
  3. Review the sensors that are selected on the Configure > Sensors screen. Monitored sensors are usually just the battery but you can change that.
  4. When iCloud3 starts, it creates the appropriate sensors for a device. You will find the list of sensors created in the icloud3.log file at the beginning of the file. The are also listed in the .storage/icloud3/configuration file in the device_sensors section at the end of the list. You can also check the following to see if there are any errors:
  5. Event Log during startup shows how the devices are set up.
  6. HA Settings > System > Log shows any errors that might have occurred.
  7. HA Developer Tools > States - Look for any selsor. that ends in a _2. Also look at the device_tracker items. This occurs when iCloud3 was loaded and HA wanted to recreate the sensors. Try _iCloud3 Configure > Tools > Correct 2 errors(?) or on the HA Settings > Entities screen.

gcobb321 avatar Aug 25 '25 20:08 gcobb321

Hi,

There are no sensors at all. At first it created all the sensors for Szifonvv (which is a device retrieved from an Apple account where no family sharing), but the sensors created for this already gone. I have nothing else than two sensors for the two airpods and it the location sensor. Very strange and I'm not sure of this is due to some account specific issue or something in the code. I'm using this integration for years and this is the first time I have this issue.

I have nothing interesting in log and no sign of creating sensors during the startup.

Vladx71 avatar Aug 26 '25 07:08 Vladx71

When I'm checking the log I can see it thinks sensors are created

🔻 READ JSON FILE--/CONFIG/.STORAGE/ICLOUD3/RESTORE_STATE
{"{'profile': {'version': 0, 'last_update': '2025-08-26 10:45:00', 'last_commit': '2025-08-26 10:45:10"}
08-26 10:47:00 [device_track:0132]  DEVICE TRACKERS ADDED: {'BaseName': 'device_tracker.', 'Count': 4, 'Entities': 'szifonv, vikiphone, vla**1**ad@watch, vikiwatch'}
08-26 10:47:02 [device_track:0109]  Device Tracker Entities > Created-4
08-26 10:47:03 [device_track:0585]  DEVICE TRACKER REMOVED: szifonv
08-26 10:47:04 [device_track:0585]  DEVICE TRACKER REMOVED: vikiphone
08-26 10:47:04 [device_track:0585]  DEVICE TRACKER REMOVED: vla**1**ad@watch
08-26 10:47:05 [device_track:0585]  DEVICE TRACKER REMOVED: vikiwatch
08-26 10:47:09 [sensor………………:0114]  **Sensor Entities > Created-68, Excluded-0**

However the reality is, no sensors created at all

Image

Vladx71 avatar Aug 26 '25 08:08 Vladx71

What version are you running? I saw a similar issue where the devices Evette listed and then deleted. I believe this was fixed in v3.2.4.1 in the iCloud3 Developers repo. See iCloud3 docs, Installing iCloud3 chapter on steps to set up HACS assess to this repo.

gcobb321 avatar Aug 26 '25 16:08 gcobb321

I'm using the latest developer edition 3.2.4.1

Vladx71 avatar Aug 26 '25 17:08 Vladx71

Hmmm. And I am on a holiday for the next 2-weeks.

Turn on Debug log_level on Configure > Tools. Restart HA. Send the icloud3.log file to [email protected] after it starts up.

I have access to my development system and will see if I can send you some debug code with trace logging to see why it adds the devices and then remove them.

gcobb321 avatar Aug 26 '25 18:08 gcobb321

The code for removing a device is in the icloud3/device_tracker.py file at lines 570-575 in the remove_device function`. I want to see who is calling that function.

To do this, replace lines 570-575 with the following:

    def remove_device_tracker(self):
        # TESTCODE
        _log("-"*80)
        _log(f"REMOVING DEVICE TRACKER {self.entity_id}")
        import inspect
        _log(f"CALLED FROM FILENAME {inspect.stack()[1].filename}")
        _log(f"CALLED FROM FUNCTION {inspect.stack()[1].function}")
        _log(f"CALL STACK {inspect.stack()}")
        _log("-"*80)        
        return

        try:  
            Gb.hass.async_create_task(self.async_remove(force_remove=True))

        except Exception as err:
            log_exception(err)

Then save that file and restart HA.

This will dump a let on statements into the icloud3.log file. Send that file to [email protected] and I’ll look at it to see what is going on.

Note: The return statement after all of the _log statements will prevent the device _tracker entity from being deleted. You will not be able to delete any devices on the Configure > iCloud3 Update Devices screen . Put an # in front of it to change that to a comment to be ask to delete devices again. Save and restart HA.

gcobb321 avatar Aug 27 '25 01:08 gcobb321

I looked at the icloud3.log file and the info that should have displayed from the statements above was not there. This could be caused by the following:

  • The device was not being removed from HA by the remove_device_tracker routine you inserted the code into. This is the only place within iCloud3 that removes a device_tracker entity.
  • The device is removed somewhere else in HA.
  • Another error was encountered when that code was run.

HA will run code after it removes a device to let iCloud3 clean up any internal tables after it is removed. This is done in the `after_

  1. Edit the icloud3/device_tracker.py file again.

You should see the following statement on line 595 and the code you inserted above in lines 571-579.

        log_info_msg(f"DEVICE TRACKER REMOVED: {self.devicename}")
  1. Insert the following lines after that statement. Make sure all of the lines of code line up with the line above and they start with 8-spaces
        # TESTCODE
        _log("-"*80)
        _log(f"REMOVED DEVICE TRACKER {self.entity_id}")
        import inspect
        _log(f"CALLED FROM FILENAME {inspect.stack()[1].filename}")
        _log(f"CALLED FROM FUNCTION {inspect.stack()[1].function}")
        _log(f"CALL STACK {inspect.stack()}")
        _log("-"*80)
  1. Save the file.
  2. Restart HA.
  3. Send me the log files again.
  4. Also send me the icloud3/device_tracker.py file.
You should see there following lines in the _icloud3.log_file somewhere at the beginning of the file below the REMOVING DEVICR 08-27 22:13:47 [device_track:0595]  DEVICE TRACKER REMOVED: gary_airpods
08-27 22:13:47 [device_track:0597] ⛔.⛔ . . . -------------------------------------------------------------------------------- 
08-27 22:13:47 [device_track:0598] ⛔.⛔ . . . REMOVED DEVICE TRACKER device_tracker.gary_airpods 
08-27 22:13:47 [device_track:0600] ⛔.⛔ . . . CALLED FROM FILENAME /usr/src/homeassistant/homeassistant/helpers/entity.py 
08-27 22:13:47 [device_track:0601] ⛔.⛔ . . . CALLED FROM FUNCTION _call_on_remove_callbacks 
08-27 22:13:47 [device_track:0602] ⛔.⛔ . . . CALL STACK [FrameInfo(frame=<frame at 0x7f5ef0d970, file '/config/custom_components/icloud3/device_tracker.py', line 602, code after_removal_cleanup>, filename='/config/custom_components/icloud3/device_tracker.py', lineno=602, function='after_removal_cleanup', 
….               
08-27 22:13:47 [device_track:0603] ⛔.⛔ . . . --------------------------------------------------------------------------------

I am in London until Saturday and then get on a cruise ship. My HA server is in Florida USA.

gcobb321 avatar Aug 28 '25 02:08 gcobb321

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is:

Image

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows:

Image

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

gcobb321 avatar Aug 28 '25 19:08 gcobb321

Once a sensor has been marked as disabled, there is no way to enable it again without editing the .storage/core.entity_registry file and changing the ”disabled_by”: “device” to ”disabled_by”, null for every sensor for the device.

I added a device and then disabled it and could not find a way for the sensors to show up until I did that. Google searches all said the same thing. There were some that said to disable the integration and then reenable it. That did not work and created bigger issues.

The line will look something like this:

… “disabled_by":”device”,"entity_category":null,"entity_id":"sensor.gary_iphone_zone_name" …

Change to this:

… “disabled_by":null,"entity_category":null,"entity_id":"sensor.gary_iphone_zone_name" …

Note:

  1. The “entity _category” may be in a different part of the record and not displayed in that position
  2. Back up or copy the file before you start so you can recover if something goes wrong.
  3. Stop HA first, then edit and save and then restart HA

gcobb321 avatar Aug 29 '25 05:08 gcobb321

Thank you. I have no other option than disabling the device in config.

After I changed // sed -i 's/"disabled_by":"device"/"disabled_by":null/g' // in core registry, my sensors are back. However device tracker entities still missing and when I make any change in icloud3 config, the sensors are disabled again. Strange...

L:

On Thu, Aug 28, 2025 at 9:17 PM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is: image.png (view on web) https://github.com/user-attachments/assets/0d33240e-d129-417b-8192-a0caae4458f7

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows: image.png (view on web) https://github.com/user-attachments/assets/ee7ab598-34bc-4399-8f9a-765daf9c5b36

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2VEDB4JJYBLCFHELQL3P5ITHAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGY2TSNJQGY . You are receiving this because you authored the thread.Message ID: @.***>

Vladx71 avatar Aug 29 '25 06:08 Vladx71

Do the same thing in the ‘core.device_registry’ file for the device_tracker entities.

Gary Cobb

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 7:34:50 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101 Thank you. I have no other option than disabling the device in config.

After I changed // sed -i 's/"disabled_by":"device"/"disabled_by":null/g' // in core registry, my sensors are back. However device tracker entities still missing and when I make any change in icloud3 config, the sensors are disabled again. Strange...

L:

On Thu, Aug 28, 2025 at 9:17 PM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is: image.png (view on web) https://github.com/user-attachments/assets/0d33240e-d129-417b-8192-a0caae4458f7

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows: image.png (view on web) https://github.com/user-attachments/assets/ee7ab598-34bc-4399-8f9a-765daf9c5b36

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2VEDB4JJYBLCFHELQL3P5ITHAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGY2TSNJQGY . You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIOOVBYH4WJRP6KYDK3WC533P7YAVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZVHA4TIMJQGE. You are receiving this because you commented.Message ID: @.***>

gcobb321 avatar Aug 29 '25 08:08 gcobb321

I have no such thing in that file. It seems device tracker entities are not created.

L>

On Fri, Aug 29, 2025 at 10:44 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650 Do the same thing in the ‘core.device_registry’ file for the device_tracker entities.

Gary Cobb

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 7:34:50 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101> Thank you. I have no other option than disabling the device in config.

After I changed // sed -i 's/"disabled_by":"device"/"disabled_by":null/g' // in core registry, my sensors are back. However device tracker entities still missing and when I make any change in icloud3 config, the sensors are disabled again. Strange...

L:

On Thu, Aug 28, 2025 at 9:17 PM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is: image.png (view on web) < https://github.com/user-attachments/assets/0d33240e-d129-417b-8192-a0caae4458f7>

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows: image.png (view on web) < https://github.com/user-attachments/assets/ee7ab598-34bc-4399-8f9a-765daf9c5b36>

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB3RO2VEDB4JJYBLCFHELQL3P5ITHAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGY2TSNJQGY>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIOOVBYH4WJRP6KYDK3WC533P7YAVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZVHA4TIMJQGE>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2VKJEBK2B4VNAHCEKT3QAHFVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGIZTINRVGA . You are receiving this because you authored the thread.Message ID: @.***>

Vladx71 avatar Aug 29 '25 08:08 Vladx71

it might say it was disabled by config entry or something else. Look for the device_tracker. line and check that the disabled_by is null. Also look at the bottom of the file in the deleted section.

Gary Cobb, aka geekstergary

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 9:59:46 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233 I have no such thing in that file. It seems device tracker entities are not created.

L>

On Fri, Aug 29, 2025 at 10:44 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650 Do the same thing in the ‘core.device_registry’ file for the device_tracker entities.

Gary Cobb

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 7:34:50 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101> Thank you. I have no other option than disabling the device in config.

After I changed // sed -i 's/"disabled_by":"device"/"disabled_by":null/g' // in core registry, my sensors are back. However device tracker entities still missing and when I make any change in icloud3 config, the sensors are disabled again. Strange...

L:

On Thu, Aug 28, 2025 at 9:17 PM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is: image.png (view on web) < https://github.com/user-attachments/assets/0d33240e-d129-417b-8192-a0caae4458f7>

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows: image.png (view on web) < https://github.com/user-attachments/assets/ee7ab598-34bc-4399-8f9a-765daf9c5b36>

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB3RO2VEDB4JJYBLCFHELQL3P5ITHAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGY2TSNJQGY>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIOOVBYH4WJRP6KYDK3WC533P7YAVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZVHA4TIMJQGE>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2VKJEBK2B4VNAHCEKT3QAHFVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGIZTINRVGA . You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIOOVB5JTBMDQ4QJ2ZSDMCD3QAJAFAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGI3TMMRTGM. You are receiving this because you commented.Message ID: @.***>

gcobb321 avatar Aug 29 '25 09:08 gcobb321

I've replaced 'disabled_by:service' but still no device tracker entities.

On Fri, Aug 29, 2025 at 11:38 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236407717 it might say it was disabled by config entry or something else. Look for the device_tracker. line and check that the disabled_by is null. Also look at the bottom of the file in the deleted section.

Gary Cobb, aka geekstergary

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 9:59:46 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233> I have no such thing in that file. It seems device tracker entities are not created.

L>

On Fri, Aug 29, 2025 at 10:44 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650

Do the same thing in the ‘core.device_registry’ file for the device_tracker entities.

Gary Cobb

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 7:34:50 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101> Thank you. I have no other option than disabling the device in config.

After I changed // sed -i 's/"disabled_by":"device"/"disabled_by":null/g' // in core registry, my sensors are back. However device tracker entities still missing and when I make any change in icloud3 config, the sensors are disabled again. Strange...

L:

On Thu, Aug 28, 2025 at 9:17 PM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506>

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is: image.png (view on web) <

https://github.com/user-attachments/assets/0d33240e-d129-417b-8192-a0caae4458f7>

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows: image.png (view on web) <

https://github.com/user-attachments/assets/ee7ab598-34bc-4399-8f9a-765daf9c5b36>

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

— Reply to this email directly, view it on GitHub < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AB3RO2VEDB4JJYBLCFHELQL3P5ITHAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGY2TSNJQGY>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101>,

or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AIOOVBYH4WJRP6KYDK3WC533P7YAVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZVHA4TIMJQGE>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB3RO2VKJEBK2B4VNAHCEKT3QAHFVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGIZTINRVGA>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIOOVB5JTBMDQ4QJ2ZSDMCD3QAJAFAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGI3TMMRTGM>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236407717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2SDXNI4F4AFSJWKHCT3QANSVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGQYDONZRG4 . You are receiving this because you authored the thread.Message ID: @.***>

Vladx71 avatar Aug 30 '25 07:08 Vladx71

Try deleting it in iCloud3 and then readding it. You may just have to change the entity name so HA creates a new entity with a new name that has never been disabled.

Gary Cobb, aka geekstergary

From: Laszlo Pal @.> Sent: Saturday, August 30, 2025 8:13:13 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)https://github.com/gcobb321/icloud3/issues/495#issuecomment-3239021235 I've replaced 'disabled_by:service' but still no device tracker entities.

On Fri, Aug 29, 2025 at 11:38 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236407717 it might say it was disabled by config entry or something else. Look for the device_tracker. line and check that the disabled_by is null. Also look at the bottom of the file in the deleted section.

Gary Cobb, aka geekstergary

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 9:59:46 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233> I have no such thing in that file. It seems device tracker entities are not created.

L>

On Fri, Aug 29, 2025 at 10:44 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650

Do the same thing in the ‘core.device_registry’ file for the device_tracker entities.

Gary Cobb

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 7:34:50 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101> Thank you. I have no other option than disabling the device in config.

After I changed // sed -i 's/"disabled_by":"device"/"disabled_by":null/g' // in core registry, my sensors are back. However device tracker entities still missing and when I make any change in icloud3 config, the sensors are disabled again. Strange...

L:

On Thu, Aug 28, 2025 at 9:17 PM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506>

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is: image.png (view on web) <

https://github.com/user-attachments/assets/0d33240e-d129-417b-8192-a0caae4458f7>

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows: image.png (view on web) <

https://github.com/user-attachments/assets/ee7ab598-34bc-4399-8f9a-765daf9c5b36>

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

— Reply to this email directly, view it on GitHub < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AB3RO2VEDB4JJYBLCFHELQL3P5ITHAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGY2TSNJQGY>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101>,

or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AIOOVBYH4WJRP6KYDK3WC533P7YAVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZVHA4TIMJQGE>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB3RO2VKJEBK2B4VNAHCEKT3QAHFVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGIZTINRVGA>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIOOVB5JTBMDQ4QJ2ZSDMCD3QAJAFAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGI3TMMRTGM>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236407717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2SDXNI4F4AFSJWKHCT3QANSVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGQYDONZRG4 . You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/gcobb321/icloud3/issues/495#issuecomment-3239021235, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIOOVBY53J6TXV63Y4ICIUT3QFFITAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZZGAZDCMRTGU. You are receiving this because you commented.Message ID: @.***>

gcobb321 avatar Aug 30 '25 09:08 gcobb321

After removing device it still shows in this list, however when I adding it with a different name (SzifonVVV) it seems created everything including device tracker

[image: image.png]

On Sat, Aug 30, 2025 at 11:11 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3239138194 Try deleting it in iCloud3 and then readding it. You may just have to change the entity name so HA creates a new entity with a new name that has never been disabled.

Gary Cobb, aka geekstergary

From: Laszlo Pal @.> Sent: Saturday, August 30, 2025 8:13:13 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3239021235> I've replaced 'disabled_by:service' but still no device tracker entities.

On Fri, Aug 29, 2025 at 11:38 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236407717

it might say it was disabled by config entry or something else. Look for the device_tracker. line and check that the disabled_by is null. Also look at the bottom of the file in the deleted section.

Gary Cobb, aka geekstergary

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 9:59:46 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233> I have no such thing in that file. It seems device tracker entities are not created.

L>

On Fri, Aug 29, 2025 at 10:44 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650>

Do the same thing in the ‘core.device_registry’ file for the device_tracker entities.

Gary Cobb

From: Laszlo Pal @.> Sent: Friday, August 29, 2025 7:34:50 AM To: gcobb321/icloud3 @.> Cc: Gary Cobb @.>; Comment @.> Subject: Re: [gcobb321/icloud3] Sensor entities not created (Issue #495)

[https://avatars.githubusercontent.com/u/7804778?s=20&v=4]Vladx71 left a comment (gcobb321/icloud3#495)< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101>

Thank you. I have no other option than disabling the device in config.

After I changed // sed -i 's/"disabled_by":"device"/"disabled_by":null/g' // in core registry, my sensors are back. However device tracker entities still missing and when I make any change in icloud3 config, the sensors are disabled again. Strange...

L:

On Thu, Aug 28, 2025 at 9:17 PM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506>

I have figured it out and duplicated the problem. HA is deleting the device because it has been disabled.

My iCloud3 integrations screen is: image.png (view on web) <

https://github.com/user-attachments/assets/0d33240e-d129-417b-8192-a0caae4458f7>

However Gary-AirPods has been disabled. It is tracked by iCloud3 but the Device Tracker entity is added by iCloud3 and then removed, just like your devices. HA gives no indication on the integration screen that a device is disabled except for the lack of sensors for that device.

Clicking on Gary-AirPods shows: image.png (view on web) <

https://github.com/user-attachments/assets/ee7ab598-34bc-4399-8f9a-765daf9c5b36>

Clicking Enable reenables the device. BUT HA is not changing the disabled status in the HA entity registry for all of its sensors back to enabled so they still do not show up again. I am looking at this further.

Go to each device on the iCloud3 integration screen and see if the ‘Enable’ button in orange is displayed. If so, click it and enable the device. Restart HA a few times. Maybe it will work for you.

Also, edit the device_tracker.py file and change line 579 from return to #return.

— Reply to this email directly, view it on GitHub < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3234659506>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AB3RO2VEDB4JJYBLCFHELQL3P5ITHAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZUGY2TSNJQGY>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3235894101>,

or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AIOOVBYH4WJRP6KYDK3WC533P7YAVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZVHA4TIMJQGE>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub < https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236234650>,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/AB3RO2VKJEBK2B4VNAHCEKT3QAHFVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGIZTINRVGA>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236276233>,

or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AIOOVB5JTBMDQ4QJ2ZSDMCD3QAJAFAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGI3TMMRTGM>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3236407717,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB3RO2SDXNI4F4AFSJWKHCT3QANSVAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZWGQYDONZRG4>

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub< https://github.com/gcobb321/icloud3/issues/495#issuecomment-3239021235>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AIOOVBY53J6TXV63Y4ICIUT3QFFITAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZZGAZDCMRTGU>.

You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3239138194, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2UW4Y5BTLM4VZ5R7KL3QFTCZAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMZZGEZTQMJZGQ . You are receiving this because you authored the thread.Message ID: @.***>

Vladx71 avatar Aug 31 '25 05:08 Vladx71

The image was not displayed. If it was the Configure > iCloud3 Devices screen, delete that device from iCloud3 on that screen using the DELETE DEVICE option.

gcobb321 avatar Sep 01 '25 23:09 gcobb321

Yes, this is what I did. However the devices and entities are not removed from HA databases and stays visible in iCloud3 and cannot be deleted anymore.

On Tue, Sep 2, 2025 at 1:50 AM Gary Cobb @.***> wrote:

gcobb321 left a comment (gcobb321/icloud3#495) https://github.com/gcobb321/icloud3/issues/495#issuecomment-3243414839

The image was not displayed. If it was the Configure > iCloud3 Devices screen, delete that device from iCloud3 on that screen using the DELETE DEVICE option.

— Reply to this email directly, view it on GitHub https://github.com/gcobb321/icloud3/issues/495#issuecomment-3243414839, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3RO2SPNE7L7UXDG7LCBVL3QTLTFAVCNFSM6AAAAACEXB4EQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBTGQYTIOBTHE . You are receiving this because you authored the thread.Message ID: @.***>

Vladx71 avatar Sep 02 '25 07:09 Vladx71