Philips Hue integration stopped working all of a sudden after core update today

abhi.ko · December 4, 2021, 1:17pm

Hue stooped working after I updated Core today morning. Log details below, can someon point me to what is wrong?

Logger: homeassistant.config_entries
Source: helpers/device_registry.py:131
First occurred: 7:12:22 AM (1 occurrences)
Last logged: 7:12:22 AM

Error setting up entry Philips hue for hue
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 313, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/hue/__init__.py", line 24, in async_setup_entry
    if not await bridge.async_initialize_bridge():
  File "/usr/src/homeassistant/homeassistant/components/hue/bridge.py", line 104, in async_initialize_bridge
    await async_setup_devices(self)
  File "/usr/src/homeassistant/homeassistant/components/hue/v2/device.py", line 76, in async_setup_devices
    known_devices = [add_device(hue_device) for hue_device in dev_controller]
  File "/usr/src/homeassistant/homeassistant/components/hue/v2/device.py", line 76, in <listcomp>
    known_devices = [add_device(hue_device) for hue_device in dev_controller]
  File "/usr/src/homeassistant/homeassistant/components/hue/v2/device.py", line 57, in add_device
    return dev_reg.async_get_or_create(config_entry_id=entry.entry_id, **params)
  File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 325, in async_get_or_create
    connections = _normalize_connections(connections)
  File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 873, in _normalize_connections
    return {
  File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 874, in <setcomp>
    (key, format_mac(value)) if key == CONNECTION_NETWORK_MAC else (key, value)
  File "/usr/src/homeassistant/homeassistant/helpers/device_registry.py", line 131, in format_mac
    if len(to_test) == 17 and to_test.count(":") == 5:
TypeError: object of type 'NoneType' has no len()

abhi.ko · December 5, 2021, 4:27am

Bump - anyone else with this problem?

123 · December 5, 2021, 4:35am

Which version are you using now?

FWIW, I’m using 2021.11.3 and the Hue integration is working well (no errors like the one you posted).

abhi.ko · December 5, 2021, 4:39am

I am on Core Version: core-2021.12.0b0

123 · December 5, 2021, 4:45am

You’re running a beta version. It might have been worth mentioning that in the first post and might explain why no one replied to your question (until now) because no one has experienced the problem with the release version.

The beta version contains a revised version of the Hue integration based on a new API. You should report the problem in the Core repository on GitHub.

abhi.ko · December 5, 2021, 4:55am

Okay - just did that and reported. Any links available to documentation/discussion of the revised Hue integration with the new API?

abhi.ko · December 5, 2021, 4:59am

Also I tried restoring to a backup, but my SmartThings integration broke when I did that, Hue is now working. Anyways of fixing this without having to reinstall SmartThings from scratch.

Logger: homeassistant.config_entries
Source: components/smartthings/__init__.py:121
First occurred: 10:44:50 PM (1 occurrences)
Last logged: 10:44:50 PM

Error setting up entry Home for smartthings
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 304, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/components/smartthings/__init__.py", line 121, in async_setup_entry
    token = await api.generate_tokens(
  File "/usr/local/lib/python3.9/site-packages/pysmartthings/smartthings.py", line 209, in generate_tokens
    result = await self._service.generate_tokens(
  File "/usr/local/lib/python3.9/site-packages/pysmartthings/api.py", line 424, in generate_tokens
    raise APIInvalidGrant(data.get("error_description"))
pysmartthings.errors.APIInvalidGrant: Invalid refresh token: 3873b21kb2872ybwsvws252

123 · December 5, 2021, 5:00am

All I know about it is limited to what I read in the PR that implemented it:

github.com/home-assistant/core

Refactor of Hue integration with full V2 support

home-assistant:dev ← marcelveldt:hue-v2

opened 03:32PM - 03 Nov 21 UTC

marcelveldt

+7163 -2272

## Breaking change - The "hue.activate_scene" service is now deprecated for V…2 bridges. Scenes from Hue will be added to HA as scene entities. The service stays available for V1 bridges but will be removed for V2 bridges in a future release. - The configuration options for the Hue integration are removed for V2 bridges as they no longer made any sense and/or are now handled in a more generic Home Assistant native approach: -- Lights created from Hue groups/rooms will be imported but disabled by default. -- Grouped lights will by default handle unavailable lights as part of the group. - If you're using the event "hue_event" to catch button presses for e.g. a Hue remote/button: The emitted id's are now a bit different as Hue simplified the type of events these devices emit. from device specific into a more generic approach: -- The type will now contain the sort of button press (e.g. short press, release etc.) -- The subtype will contain the button number. For a Hue Dimmer switch for example, the top button will be 1, while the bottom button will be 4. If the device only has one button, this number will always be 1. ## Proposed change Hue is phasing out the current V1 api in favor of their new V2 Clip API, including events being pushed instead of hammering the bridge to poll changes. The aiohue library has been rewritten to the full V2 api, while still supporting V1 style for older bridges. The Home Assistant integration needs to adopt the new V2 implementation with auto switching to the correct version. That's what this PR is all about. Related to https://github.com/home-assistant-libs/aiohue/pull/74 ### All changes - The Hue integration now supports the V2 API for bridges that support it (V2 Hue bridge with latest firmware). See: https://developers.meethue.com/new-hue-api/ - The integration's logic for controlling V1 (previous implementation) and V2 has been split up. - If your bridge supports V2, the integration will automatically use that implementation, otherwise it will fallback to the previous V1 version. - The new V2 API has new (finally true unique) id's for all devices and entities. The integration will automatically migrate your previous entities. - Scenes from Hue will be added to HA as scene entities for V2 bridges, including support for Hue's new dynamic scenes. - The "hue.activate_scene" service is now deprecated for V2 bridges. The service stays available for V1 bridges but will be removed for V2 bridges in a future release. - The V2 implementation does not get any active development anymore (following Hue's decision to stop support on the V1 bridges. - The V2 implementation contains (or lays foundation for) all new features Hue is adding to their API, such as gradient lights. - The "reachable" property on Hue lights is replaced by a separate sensor with the zigbee connectivity. - The Hue bridge is no longer polled for state, instead all changes will be pushed, resulting in a smoother user experience and less stress on the Hue bridge. ## Type of change - [X] Dependency upgrade - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New integration (thank you!) - [X] New feature (which adds functionality to an existing integration) - [ ] Breaking change (fix/feature causing existing functionality to break) - [X] Code quality improvements to existing code or addition of tests ## Additional information In "V2 mode" the bridge will no longer be polled for state, all state changes come in instantly. The current implementation is still hammering the bridge with requests even if events are streamed. This is now fixed. Although the scope for this PR is to (only) implement all current integration platforms/features with the V2 api/library, a few new features are available: - Import of Hue scenes as scene entities, including support for Hue's new "dynamic" scenes. - A few more sensors are detected because of the simple fact that the new API provides more states. Possible Future update(s) in follow-up PR's - library support already there - Read status of and control entertainment areas - Controlling gradient lights ## Checklist - [X] The code change is tested and works locally. - [X] Local tests pass. **Your PR cannot be merged unless tests pass** - [X] There is no commented out code in this PR. - [X] I have followed the [development checklist][dev-checklist] - [X] The code has been formatted using Black (`black --fast homeassistant tests`) - [x] Tests have been added to verify that the new code works. - [X] Untested files have been added to `.coveragerc`. ## TODO: - [x] Add tests for all V2 code - [x] Add test for migration logic - [x] Add test for auto switching V1 --> V2 - [x] Add hue scene event on button events for V2 implementation The integration reached or maintains the following [Integration Quality Scale][quality-scale]: Once tests are added: - [ ] No score or internal - [ ] 🥈 Silver - [ ] 🥇 Gold - [X] 🏆 Platinum - [X] I have reviewed two other [open pull requests][prs] in this repository.

abhi.ko · December 5, 2021, 5:11am

Thank You.

Chris_Sanner · December 17, 2021, 3:25pm

I’m having significant issues with this change - when I turn off a light the light goes out, but the toggle flips back to “on” repeatedly. Lights become unavailable that don’t appear as unavailable in the hue app.
Some behaviors might just be things I need to get used to but these two are extremely frustrating and feel like my home is now “broken”

123 · December 17, 2021, 4:19pm

Ensure you have upgraded to 2021.12.3 which is supposed to correct the majority of reported problems with the new Hue integration.

If you are using the .3 patch release and still have problems, report them as an Issue in the Core repo on GitHub. The integration’s author has been very helpful and responsive.

Chris_Sanner · December 18, 2021, 5:32am

I have upgraded. it is a bit better, but still fiddly
I’ll report some issues I’m still seeing
thanks!