Integration shows up twice

TheLion commented 6 months ago

I already was using the integration In HA. After the update it shows up twice. Once for the already running integration and it finds a new device, prompting to configure it.

The existing integration seems to work fine for now.

Also, when I try to configure the new device, it keeps asking for the pin, event though I am sure it is the correct one. Also refreshed the pin and used that one.

How to continue?

Thanks for assisting.

Regards,

Martijn

JackJPowell commented 6 months ago

Hi @TheLion,

The easy answer is to just ignore the discovery. If you've added the integration manually, this could be the zero conf discovery protocol surfacing the same remote. However, the PIN should be working if this was the case.

Is there any chance you are running the core-simulator in a docker or something? It would also be broadcasting its presence and would of course have a different PIN from your actual remote.

JackJPowell commented 6 months ago

Alternatively, Do you have two devices listed in the integration? Maybe a first with one entity and another with 24 or so?

TheLion commented 6 months ago

Hi, No. I have one integration configured, with one device and 25 entities and one integration discovered.

TheLion commented 6 months ago

Hi @TheLion,

The easy answer is to just ignore the discovery. If you've added the integration manually, this could be the zero conf discovery protocol surfacing the same remote. However, the PIN should be working if this was the case.

Is there any chance you are running the core-simulator in a docker or something? It would also be broadcasting its presence and would of course have a different PIN from your actual remote.

No, no core configurator running or anything like that. Just the remote and the dock.

It is interesting that the pin doesn't work...

albaintor commented 6 months ago

Hi about that : in debug level, I can see that the remote can be discovered in 2 ways => through its hostname, which holds the formatted mac address and this is good because this is the key to compare to existing remotes (and avoid raising the same discovered device), but also through IP address (ipv6 in my case). And in that case there is no easy way to check after existing remotes.

Following a feature request, the UC team added the mac address in the public API in the last firmware, but when I tested a call to this API inside the async_step_zeroconf method, HA raised an error (no blocking calls should occur during this sequence). Ideally the mac address should be advertised in the zeroconf data, but the UC team told me that it was too complicated.

So at this state one may have the same device discovered again

TheLion commented 6 months ago

OK.

But what to do on such a case? Just ignore the discovered one?

JackJPowell commented 6 months ago

The short answer is yes. There are two ways that Home Assistant discovers the remote on the network and due to limitations in the data included in those broadcasts, the integration is not able to determine if they are from the same remote. If the UC team updates the zeroconf broadcast message (which they've said they are unlikely to do), this could be addressed.

@albaintor, it's been a minute since I looked at the zeroconf messages, but what about just ignoring those discovered by IP, rather than hostname? Might cut out some discoveries, but there is a fallback to just add manually.

TheLion commented 6 months ago

OK, will do that.

albaintor commented 6 months ago

@albaintor, it's been a minute since I looked at the zeroconf messages, but what about just ignoring those discovered by IP, rather than hostname? Might cut out some discoveries, but there is a fallback to just add manually.

Yes good idea , I guess that the hostname advertisement should always happen

TheLion commented 5 months ago

The new release of the integration did prevent two remotes showing up.

I now have 5 :-) 1 already active and configured from the start and 4 newly discovered.

JackJPowell commented 5 months ago

Inconceivable! 😩

Sorry man. What a weird issue. Would you mind turning on debug logging (left column at the bottom next to all the discovered remotes) then restart HA. Navigate back to the device and after it's found all four, disable logging and it will download a file. Then could you upload that here for me to take a look?

TheLion commented 5 months ago

😂 I will do that this weekend. Before they take over HA completely, as I currently have 7 🥴

TheLion commented 5 months ago

Oh. After the update of Home Assistant to 2024.4.3 an the update of the integration to 0.6.5, I have only 2 left. One active/configured and one newly discovered. I will keep and eye on it and when the multiply, perform the debug steps. Or do you want me to do that with the currently existing two?

JackJPowell commented 5 months ago

Since it's easy, would you mind toggling the 'enable debug logging' on and off? It should pull logs from before you enabled it and it will hopefully have my zeroconf logging in there.

Which additional remote name are you seeing? 4pets or just 'Remote Two'? Do you recognize the 4pets name?

TrialMaster commented 5 months ago

The new release of the integration did prevent two remotes showing up.

I now have 5 :-) 1 already active and configured from the start and 4 newly discovered.

Thanks for posting this information. I am seeing similar increase in remote discoveries since current update.

TheLion commented 5 months ago

Since it's easy, would you mind toggling the 'enable debug logging' on and off? It should pull logs from before you enabled it and it will hopefully have my zeroconf logging in there.

Which additional remote name are you seeing? 4pets or just 'Remote Two'? Do you recognize the 4pets name?

I just switched on debug and restarted HA.

2024-04-13 11:30:04.564 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration watchman which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.565 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration plex_recently_added which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.565 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration auto_backup which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.566 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration solaredgeoptimizers which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.566 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration afvalinfo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.566 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration truenas which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.567 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration entsoe which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.567 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration blitzortung which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.568 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration blueiris which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.568 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration sonarr_upcoming_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.569 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration nordpool which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.569 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration petkit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.570 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration scheduler which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.570 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.571 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration zha_toolkit which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.571 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration govee_lan which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.572 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration roborock which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.572 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration landroid_cloud which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.573 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration radarr_upcoming_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.573 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration govee which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.574 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.574 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration unfoldedcircle which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.575 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration battery_notes which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.575 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.575 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration moonraker which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.575 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration frank_energie which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:04.576 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration wundergroundpws which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-04-13 11:30:07.740 WARNING (ImportExecutor_0) [homeassistant.const] ENERGY_KILO_WATT_HOUR was used from entsoe, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfEnergy.KILO_WATT_HOUR instead, please report it to the author of the 'entsoe' custom integration
2024-04-13 11:30:07.936 WARNING (SyncWorker_6) [custom_components.truenas.truenas_api] TrueNAS truenas.fourpets.net unable to fetch data "reporting/get_data" (422)
2024-04-13 11:30:08.431 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'hacs' accesses hass.components.frontend. This is deprecated and will stop working in Home Assistant 2024.9, it should be updated to import functions used from frontend directly at custom_components/hacs/frontend.py, line 68: hass.components.frontend.async_register_built_in_panel(, please create a bug report at https://github.com/hacs/integration/issues
2024-04-13 11:30:09.822 WARNING (ImportExecutor_0) [homeassistant.const] LENGTH_KILOMETERS was used from blitzortung, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfLength.KILOMETERS instead, please report it to the author of the 'blitzortung' custom integration
2024-04-13 11:30:09.826 WARNING (ImportExecutor_0) [homeassistant.const] LENGTH_MILES was used from blitzortung, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfLength.MILES instead, please report it to the author of the 'blitzortung' custom integration
2024-04-13 11:30:10.809 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] Finished fetching unfoldedcircle data in 0.000 seconds (success: True)
2024-04-13 11:30:11.787 ERROR (MainThread) [homeassistant.components.script] Blueprint 'Confirmable Notification' generated invalid script with inputs {'notify_device': '66b7dd3593be97dfff20c2c6c86d51f7', 'confirm_text': 'OK', 'dismiss_text': 'Annuleren', 'message': 'Bericht', 'title': 'Titel'}: Unknown device '66b7dd3593be97dfff20c2c6c86d51f7'
2024-04-13 11:30:13.090 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee_lan.light.GoveLightEntity'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.RGB: 'rgb'>, <ColorMode.BRIGHTNESS: 'brightness'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-04-13 11:30:13.091 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee_lan.light.GoveLightEntity'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.RGB: 'rgb'>, <ColorMode.BRIGHTNESS: 'brightness'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-04-13 11:30:13.091 WARNING (MainThread) [homeassistant.components.light] None (<class 'custom_components.govee_lan.light.GoveLightEntity'>) sets invalid supported color modes {<ColorMode.COLOR_TEMP: 'color_temp'>, <ColorMode.RGB: 'rgb'>, <ColorMode.BRIGHTNESS: 'brightness'>}, this will stop working in Home Assistant Core 2025.3, please create a bug report at https://github.com/wez/govee-lan-hass/issues
2024-04-13 11:30:13.391 WARNING (ImportExecutor_0) [zhaquirks] Loaded custom quirks. Please contribute them to https://github.com/zigpy/zha-device-handlers
2024-04-13 11:30:13.419 WARNING (ImportExecutor_0) [homeassistant.const] LENGTH_KILOMETERS was used from blitzortung, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfLength.KILOMETERS instead, please report it to the author of the 'blitzortung' custom integration
2024-04-13 11:30:13.461 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_current_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.466 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_next_hour_electricity_market_price (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.469 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_lowest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.474 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_highest_energy_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.491 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_average_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.498 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-13 11:30:13.498 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_current_percentage_of_highest_electricity_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('monetary') it is using; expected None or one of 'total'; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.508 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-13 11:30:13.508 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_time_of_highest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.515 WARNING (MainThread) [custom_components.entsoe.sensor] Unable to update entity due to data processing error: None and error: min() iterable argument is empty
2024-04-13 11:30:13.515 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.dynamische_energie_tarieven_time_of_lowest_price_today (<class 'custom_components.entsoe.sensor.EntsoeSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/JaccoR/hass-entso-e/issues
2024-04-13 11:30:13.569 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] Unfolded Circle Remote events list to subscribe ['software_updates', 'entity_activity', 'activity_groups', 'battery_status', 'ambient_light', 'configuration', 'entity_media_player']
2024-04-13 11:30:13.579 WARNING (ImportExecutor_0) [homeassistant.const] DATA_GIBIBYTES was used from truenas, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfInformation.GIBIBYTES instead, please report it to the author of the 'truenas' custom integration
2024-04-13 11:30:13.583 WARNING (ImportExecutor_0) [homeassistant.const] DATA_KIBIBYTES was used from truenas, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfInformation.KIBIBYTES instead, please report it to the author of the 'truenas' custom integration
2024-04-13 11:30:13.587 WARNING (ImportExecutor_0) [homeassistant.const] TEMP_CELSIUS was used from truenas, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfTemperature.CELSIUS instead, please report it to the author of the 'truenas' custom integration
2024-04-13 11:30:13.637 ERROR (MainThread) [homeassistant.components.binary_sensor] rpi_power: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 707, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1270, in async_device_update
    await hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/rpi_power/binary_sensor.py", line 53, in update
    value = self._under_voltage.get()
            ^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'get'
2024-04-13 11:30:13.801 WARNING (ImportExecutor_0) [homeassistant.const] LENGTH_KILOMETERS was used from blitzortung, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfLength.KILOMETERS instead, please report it to the author of the 'blitzortung' custom integration
2024-04-13 11:30:13.814 WARNING (ImportExecutor_0) [homeassistant.const] LENGTH_MILES was used from blitzortung, this is a deprecated constant which will be removed in HA Core 2025.1. Use UnitOfLength.MILES instead, please report it to the author of the 'blitzortung' custom integration
2024-04-13 11:30:14.092 WARNING (ImportExecutor_0) [homeassistant.components.camera] SUPPORT_STREAM was used from blueiris, this is a deprecated constant which will be removed in HA Core 2025.1. Use CameraEntityFeature.STREAM instead, please report it to the author of the 'blueiris' custom integration
2024-04-13 11:30:14.097 WARNING (ImportExecutor_0) [homeassistant.components.camera] SUPPORT_STREAM was used from blueiris, this is a deprecated constant which will be removed in HA Core 2025.1. Use CameraEntityFeature.STREAM instead, please report it to the author of the 'blueiris' custom integration
2024-04-13 11:30:14.293 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] Manually updated unfoldedcircle data
2024-04-13 11:30:14.294 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] UC2 debug structure
Media player entities from remote :
 - Player ATV4K Woonkamer (uc_appletv_driver.main.F0:B3:EC:09:D1:46) : OFF
 - Player Denon AVC-X3700H (uc_denon_driver.main.media_player.DBCG012114780) : OFF
 - Player KM7 (uc_androidtv_driver.main.222243BDF815) : OFF
2024-04-13 11:30:14.337 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_all_cameras (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.337 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_all_cameras_cycle (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.337 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_house_hd (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.338 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_3d_printers (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.338 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_achtertuin (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.338 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_carport (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.338 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_woonkamer (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.339 WARNING (MainThread) [homeassistant.helpers.entity] Entity camera.fourpets_zolder (<class 'custom_components.blueiris.camera.BlueIrisCamera'>) is using deprecated supported features values which will be removed in HA Core 2025.1. Instead it should use <CameraEntityFeature: 0>, please create a bug report at https://github.com/elad-bar/ha-blueiris/issues and reference https://developers.home-assistant.io/blog/2023/12/28/support-feature-magic-numbers-deprecation
2024-04-13 11:30:14.408 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] Manually updated unfoldedcircle data
2024-04-13 11:30:14.408 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] UC2 debug structure
Media player entities from remote :
 - Player ATV4K Woonkamer (uc_appletv_driver.main.F0:B3:EC:09:D1:46) : OFF
 - Player Denon AVC-X3700H (uc_denon_driver.main.media_player.DBCG012114780) : OFF
 - Player KM7 (uc_androidtv_driver.main.222243BDF815) : OFF
2024-04-13 11:30:15.025 WARNING (zeroconf-ServiceBrowser-_googlecast._tcp-132) [pychromecast.dial] Failed to determine cast type for host <unknown> (HTTP Error 403: Forbidden) (services:{MDNSServiceInfo(name='KM7-a4b4f662d99794a3b096f3690a19bb6a._googlecast._tcp.local.')})
2024-04-13 11:30:17.171 WARNING (MainThread) [aioesphomeapi.reconnect_logic] Can't connect to ESPHome API for everything-presence-one-f0f058 @ 192.168.206.221: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.206.221', port=6053))]: [Errno 113] Connect call failed ('192.168.206.221', 6053) (SocketAPIError)
2024-04-13 11:30:19.092 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] Manually updated unfoldedcircle data
2024-04-13 11:30:19.093 DEBUG (MainThread) [custom_components.unfoldedcircle.coordinator] UC2 debug structure
Media player entities from remote :
 - Player ATV4K Woonkamer (uc_appletv_driver.main.F0:B3:EC:09:D1:46) : OFF
 - Player Denon AVC-X3700H (uc_denon_driver.main.media_player.DBCG012114780) : OFF
 - Player KM7 (uc_androidtv_driver.main.222243BDF815) : OFF
2024-04-13 11:30:22.803 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0xEF53:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
2024-04-13 11:30:22.804 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x2443:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
2024-04-13 11:30:22.804 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x845D:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
2024-04-13 11:30:22.808 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0xEF53:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
2024-04-13 11:30:22.808 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x2443:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
2024-04-13 11:30:22.809 WARNING (MainThread) [homeassistant.components.zha.core.cluster_handlers] [0x845D:2:0x0300]: [Min mireds is 0, setting to 153] Please open an issue on the quirks repo to have this device corrected
2024-04-13 11:30:23.534 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/google_travel_time/sensor.py", line 140, in first_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/google_travel_time/sensor.py", line 169, in update
    self._matrix = distance_matrix(
                   ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/googlemaps/distance_matrix.py", line 130, in distance_matrix
    return client._request("/maps/api/distancematrix/json", params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/googlemaps/client.py", line 253, in _request
    result = self._get_body(response)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/googlemaps/client.py", line 279, in _get_body
    raise googlemaps.exceptions.ApiError(api_status,
googlemaps.exceptions.ApiError: REQUEST_DENIED (You must enable Billing on the Google Cloud Project at https://console.cloud.google.com/project/_/billing/enable Learn more at https://developers.google.com/maps/gmp-get-started)
2024-04-13 11:30:23.536 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/google_travel_time/sensor.py", line 140, in first_update
    await self.hass.async_add_executor_job(self.update)
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/google_travel_time/sensor.py", line 169, in update
    self._matrix = distance_matrix(
                   ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/googlemaps/distance_matrix.py", line 130, in distance_matrix
    return client._request("/maps/api/distancematrix/json", params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/googlemaps/client.py", line 253, in _request
    result = self._get_body(response)
             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/googlemaps/client.py", line 279, in _get_body
    raise googlemaps.exceptions.ApiError(api_status,
googlemaps.exceptions.ApiError: REQUEST_DENIED (You must enable Billing on the Google Cloud Project at https://console.cloud.google.com/project/_/billing/enable Learn more at https://developers.google.com/maps/gmp-get-started)
2024-04-13 11:30:23.702 DEBUG (MainThread) [custom_components.unfoldedcircle.config_flow] Unfolded circle remote found d01769834a99 192.168.206.125 ZeroconfServiceInfo(ip_address=ZeroconfIPv4Address('192.168.206.125'), ip_addresses=[ZeroconfIPv4Address('192.168.206.125'), ZeroconfIPv6Address('fd61:967a:64f1:d70:d217:69ff:fe83:4a99')], port=80, hostname='RemoteTwo-d01769834a99.local.', type='_uc-remote._tcp.local.', name='RemoteTwo-d01769834a99._uc-remote._tcp.local.', properties={'ver': 'v0.41.4-beta', 'ver_api': '0.31.3', 'https_port': '443', 'model': 'UCR2'}) :
2024-04-13 11:30:23.862 DEBUG (MainThread) [custom_components.unfoldedcircle.config_flow] Unfolded Circle Zeroconf Creating: d01769834a99 ZeroconfServiceInfo(ip_address=ZeroconfIPv4Address('192.168.206.125'), ip_addresses=[ZeroconfIPv4Address('192.168.206.125'), ZeroconfIPv6Address('fd61:967a:64f1:d70:d217:69ff:fe83:4a99')], port=80, hostname='RemoteTwo-d01769834a99.local.', type='_uc-remote._tcp.local.', name='RemoteTwo-d01769834a99._uc-remote._tcp.local.', properties={'ver': 'v0.41.4-beta', 'ver_api': '0.31.3', 'https_port': '443', 'model': 'UCR2'})

I now only had two remotes ;-)

The name 4Pets is what I called my remote on the remote itself , so that is recognizable. I haven't really founds any pattern in the names of the discovered remotes.

If you need any more info, please feel free to ask.

JackJPowell commented 5 months ago

Thanks for sharing.

This log contained a zeroconf discovery of a single remote at IP address: 192.168.206.125 (MAC: d01769834a99) but it did treat it as unique.

Could you also send me the diagnostic info from HA for the remote? If you go to the device page and then click the three-dots overflow menu you'll see an option to download diagnostics. Screenshot 2024-04-13 at 9 22 37 AM

TheLion commented 5 months ago

That's the IP of my remote.

Below the diagnostics


{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2024.4.3",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.12.2",
    "docker": true,
    "arch": "x86_64",
    "timezone": "Europe/Amsterdam",
    "os_name": "Linux",
    "os_version": "6.6.20-haos",
    "supervisor": "2024.04.0",
    "host_os": "Home Assistant OS 12.1",
    "docker_version": "24.0.7",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "watchman": {
      "version": "0.5.1",
      "requirements": [
        "prettytable==3.0.0"
      ]
    },
    "plex_recently_added": {
      "version": "0.3.8",
      "requirements": []
    },
    "auto_backup": {
      "version": "1.4.1",
      "requirements": []
    },
    "solaredgeoptimizers": {
      "version": "1.2.2",
      "requirements": [
        "solaredgeoptimizers==1.0.12",
        "jsonfinder==0.4.2"
      ]
    },
    "afvalinfo": {
      "version": "2.0.8",
      "requirements": [
        "Babel==2.8.0",
        "python-dateutil==2.8.1"
      ]
    },
    "truenas": {
      "version": "0.0.0",
      "requirements": []
    },
    "entsoe": {
      "version": "0.0.1",
      "requirements": [
        "entsoe-py==0.5.8"
      ]
    },
    "blitzortung": {
      "version": "1.0.1",
      "requirements": [
        "paho-mqtt>=1.5.0"
      ]
    },
    "blueiris": {
      "version": "1.0.16",
      "requirements": []
    },
    "sonarr_upcoming_media": {
      "version": "0.2.8",
      "requirements": []
    },
    "nordpool": {
      "version": "0.0.14",
      "requirements": [
        "nordpool>=0.2",
        "backoff"
      ]
    },
    "petkit": {
      "version": "0.1.10",
      "requirements": [
        "petkitaio==0.1.10",
        "tzlocal>=4.2"
      ]
    },
    "scheduler": {
      "version": "v0.0.0",
      "requirements": []
    },
    "frigate": {
      "version": "5.1.0",
      "requirements": [
        "pytz"
      ]
    },
    "zha_toolkit": {
      "version": "v1.1.10",
      "requirements": [
        "pytz"
      ]
    },
    "govee_lan": {
      "version": "1.0.0",
      "requirements": [
        "govee-led-wez>=0.0.15"
      ]
    },
    "roborock": {
      "version": "1.0.13",
      "requirements": [
        "python-roborock==0.36.0",
        "ical==6.1.0",
        "dacite==1.8.0"
      ]
    },
    "landroid_cloud": {
      "version": "4.0.6",
      "requirements": [
        "pyworxcloud==4.1.10"
      ]
    },
    "radarr_upcoming_media": {
      "version": "0.3.6",
      "requirements": []
    },
    "govee": {
      "version": "2023.11.1",
      "requirements": [
        "govee-api-laggat==0.2.2",
        "dacite==1.8.0"
      ]
    },
    "nodered": {
      "version": "3.1.5",
      "requirements": []
    },
    "unfoldedcircle": {
      "version": "v0.6.5",
      "requirements": [
        "websockets==12.0",
        "pyUnfoldedCircleRemote==0.6.5"
      ]
    },
    "battery_notes": {
      "version": "2.2.5",
      "requirements": []
    },
    "hacs": {
      "version": "1.34.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "moonraker": {
      "version": "1.2.0",
      "requirements": [
        "moonraker-api==2.0.5"
      ]
    },
    "frank_energie": {
      "version": "3.0.0",
      "requirements": [
        "python-frank-energie==6.0.0"
      ]
    },
    "wundergroundpws": {
      "version": "2.0.4",
      "requirements": []
    }
  },
  "integration_manifest": {
    "domain": "unfoldedcircle",
    "name": "Unfolded Circle",
    "codeowners": [
      "@jackjpowell"
    ],
    "config_flow": true,
    "dependencies": [
      "network",
      "zeroconf"
    ],
    "version": "v0.6.5",
    "documentation": "https://github.com/JackJPowell/hass-unfoldedcircle",
    "homekit": {},
    "integration_type": "device",
    "iot_class": "local_push",
    "requirements": [
      "websockets==12.0",
      "pyUnfoldedCircleRemote==0.6.5"
    ],
    "ssdp": [],
    "zeroconf": [
      "_uc-remote._tcp.local."
    ],
    "is_built_in": false
  },
  "data": {
    "endpoint": "http://192.168.206.125/api/",
    "configuration_url": "http://192.168.206.125/configurator/",
    "apikey": "**REDACTED**",
    "pin": "**REDACTED**",
    "activity_groups": [],
    "activities": [
      {
        "__type": "<class 'pyUnfoldedCircleRemote.remote.Activity'>",
        "repr": "<pyUnfoldedCircleRemote.remote.Activity object at 0x7f0ed5b2d6a0>"
      },
      {
        "__type": "<class 'pyUnfoldedCircleRemote.remote.Activity'>",
        "repr": "<pyUnfoldedCircleRemote.remote.Activity object at 0x7f0ed490c5f0>"
      },
      {
        "__type": "<class 'pyUnfoldedCircleRemote.remote.Activity'>",
        "repr": "<pyUnfoldedCircleRemote.remote.Activity object at 0x7f0ed5b2da00>"
      }
    ],
    "_entities": [
      {
        "__type": "<class 'pyUnfoldedCircleRemote.remote.UCMediaPlayerEntity'>",
        "repr": "<pyUnfoldedCircleRemote.remote.UCMediaPlayerEntity object at 0x7f0ed490c620>"
      },
      {
        "__type": "<class 'pyUnfoldedCircleRemote.remote.UCMediaPlayerEntity'>",
        "repr": "<pyUnfoldedCircleRemote.remote.UCMediaPlayerEntity object at 0x7f0ed490c650>"
      },
      {
        "__type": "<class 'pyUnfoldedCircleRemote.remote.UCMediaPlayerEntity'>",
        "repr": "<pyUnfoldedCircleRemote.remote.UCMediaPlayerEntity object at 0x7f0ed3571ac0>"
      }
    ],
    "_name": "4Pets Remote Two",
    "_model_name": "Remote Two",
    "_model_number": "ucr2",
    "_serial_number": "00000840",
    "_hw_revision": "rev2",
    "_manufacturer": "Unfolded Circle",
    "_mac_address": "",
    "_ip_address": "",
    "_battery_level": 94,
    "_battery_status": "CHARGING",
    "_is_charging": true,
    "_ambient_light_intensity": 6351,
    "_display_auto_brightness": true,
    "_display_brightness": 50,
    "_button_backlight": true,
    "_button_backlight_brightness": 46,
    "_sound_effects": true,
    "_sound_effects_volume": 100,
    "_haptic_feedback": true,
    "_display_timeout": 15,
    "_wakeup_sensitivity": 1,
    "_sleep_timeout": 180,
    "_update_in_progress": false,
    "_next_update_check_date": "",
    "_sw_version": "1.7.7",
    "_automatic_updates": true,
    "_available_update": [],
    "_latest_sw_version": "1.7.7",
    "_release_notes_url": "",
    "_online": true,
    "_memory_total": 1959.4140625,
    "_memory_available": 1210.87109375,
    "_storage_total": 684808200.1298828,
    "_storage_available": 4104.1298828125,
    "_cpu_load": {
      "one": 0.14,
      "five": 0.14,
      "fifteen": 0.14
    },
    "_cpu_load_one": 0.14,
    "_power_mode": "LOW_POWER",
    "_remotes": [
      {
        "name": "LG OLED55C7V",
        "entity_id": "uc.main.399318b6-2cf4-45fc-8852-1c295ec9c342"
      },
      {
        "name": "Denon",
        "entity_id": "uc.main.194a4754-dec2-4205-b1f7-fe7e36e601da"
      },
      {
        "name": "KM7 (IR)",
        "entity_id": "uc.main.532c093a-38dc-4a0a-8cdb-7486a928c62f"
      },
      {
        "name": "AppleTV ",
        "entity_id": "uc.main.19acf025-ce23-4ba1-96be-4edbe611c7dc"
      }
    ],
    "_docks": [
      {
        "name": "UC-Dock-8C4B14AA75E0",
        "device_id": "UC-Dock-8C4B14AA75E0"
      },
      {
        "name": "Remote Two",
        "device_id": "internal"
      }
    ],
    "_ir_custom": [],
    "_ir_codesets": [
      {
        "name": "LG OLED55C7V",
        "device_id": "5VjXOBe"
      },
      {
        "name": "Denon",
        "device_id": "jGENnWe"
      },
      {
        "name": "KM7 (IR)",
        "device_id": "a0341032-3b64-442d-892f-c59c83366e0a"
      },
      {
        "name": "AppleTV ",
        "device_id": "b9132e89-2b67-4fed-9f42-31db389090b1"
      }
    ],
    "_last_update_type": {
      "__type": "<enum 'RemoteUpdateType'>",
      "repr": "<RemoteUpdateType.BATTERY: 1>"
    },
    "_is_simulator": null
  }
}

TheLion commented 4 months ago

Hi,

Any update on this? After a HA restart, the remotes available procreate like bunnies, until the next restart of HA.

JackJPowell commented 4 months ago

Ok. Let's really take a look at this. Would you be able to do this for me?

Restart HA and on the unfolded circle device screen turn on debug logging.
Wait for 2 or 3 remotes to show up as available via zeroconf.
Turn off debug logging and send me the file that gets downloaded.

Zeroconf broadcasts should be filtered by mac address so you should only be seeing notifications for the number of remote you have on your network. Clearly that's not working correctly though.

TheLion commented 4 months ago

I followed your steps and I now have two additional devices showing up. Below the log. home-assistant_unfoldedcircle_2024-05-10T14-59-50.361Z.log

JackJPowell commented 4 months ago

This was not what I was expecting to find at all. The integration logs when it finds a new zeroconf discovery. (Your logs conveniently only had discoveries for the remote so if you search for the word zeroconf you'll be able to see what I'm talking about.) And what you'll see is just a single discovery with another entry informing you that it passed the uniqueness check. Meaning the MAC address of the remote it found wasn't registered with HA yet. (That's likely not true, but I can't tell much just from that)

What I needed, and expected, was another log entry stating that another zeroconf discovery was made. That way I could compare the two and figure out what was going wrong. In other words, there should be a 1 to 1 of new devices found in your HA instance and 'Unfolded circle remote found' entries in the logs you just posted. If you see 2 discoveries, there should be 2 discovery entries in the logs...

A couple of questions for you:

Do you remember when you added the remote to home assistant, did you do it manually (clicked add integration, search for Unfolded Circle, and supply url and pin) or did you add it via a zeroconf discovery?
Have you ever removed the device from HA and added it back? Would you be able to try that?

TheLion commented 4 months ago

A couple of questions for you:

Do you remember when you added the remote to home assistant, did you do it manually (clicked add integration, search for Unfolded Circle, and supply url and pin) or did you add it via a zeroconf discovery?

Not sure. I do remeber entering the pincode, so it has probably not been through zeroconf.

Have you ever removed the device from HA and added it back? Would you be able to try that?

No, I haven't. I can remove it, but when removing and re-adding, doesn't it break anything, like automations and so on?

JackJPowell commented 4 months ago

A PIN code is required for both setup flows. The manual flow requires the url of the remote.

For the re-add, if you haven't made any changes to the entity IDs you shouldn't run into any configuration issues. I'm pretty sure that any entity name changes will also be preserved so long as the ID matches.

I can try in my test environment and let you know. I'm curious too.

TheLion commented 4 months ago

A PIN code is required for both setup flows. The manual flow requires the url of the remote.

Oh. Than I am not sure which I used 😬

For the re-add, if you haven't made any changes to the entity IDs you shouldn't run into any configuration issues. I'm pretty sure that any entity name changes will also be preserved so long as the ID matches.

I can try in my test environment and let you know. I'm curious too.

That would be great.

JackJPowell commented 4 months ago

Hey @TheLion, not great news. I modified three entries:

Name and ID
Just the name
Just the icon
Created an automation referencing the ID of the changed entity

I deleted the integration and re-added it. Sadly all of my manual changes were gone and the automation was broken.

I'll leave it up to you to decide if it's worth trying this. What I can tell you is to check your entity IDs and see if you modified them. There are two kinds; IDs for activities and IDs for everything else.

Activities: <remote two name>_<activity_name> All else: <remote two name>_<entity_type>

If your entities match this format, you haven't changed them and it should be pretty safe to just delete and re-add. Let me know if you try it.

TheLion commented 4 months ago

No problem. I will create a backup of HA before I do anything, just to be sure.

I will then remove the integration and re-add it.

I will report back when I have done this.

ianhyzy commented 4 months ago

I recently removed / re-added my remote but I'm seeing this as well - sometimes I'll have 6+ prompts in HA to configure the remote. Is there something special I should try?

TheLion commented 3 months ago

I removed the integration and added it through the zeroconf option. All entities stayed the same fortunately ;-) At the moment here are no other devices discovered. I will get back in a couple of days, or earlier, if anything has or hasn't popped up.

TheLion commented 2 months ago

Time for an update. A couple of days after me previous post, we went on holiday. During the holiday, the remote was discovered again, but only once. At that time I just ignored the extra device/integration, to look at it when we got home.

It still is just one extra device that is discovered, so that's an improvement ;-)

But not sure how to continue for now.

TheLion commented 2 months ago

Cr*p. The second new device/integration just appeared. One is called "4Pets Remote Two", which is the name I gave the remote and the other is called "Remote Two".

JackJPowell / hass-unfoldedcircle

Integration shows up twice #23