Skip to content

Fix motion_area_configuration model compatibility with Hue Bridge Pro#599

Open
sporkbyspork wants to merge 1 commit intohome-assistant-libs:mainfrom
sporkbyspork:fix-bridge-pro-motion-area-config
Open

Fix motion_area_configuration model compatibility with Hue Bridge Pro#599
sporkbyspork wants to merge 1 commit intohome-assistant-libs:mainfrom
sporkbyspork:fix-bridge-pro-motion-area-config

Conversation

@sporkbyspork
Copy link
Copy Markdown

Follow-up to #546. Claude helped with understanding the codebase and with coding. This is my first PR to this project, and I'm not sure that this is the right approach.

I wanted to enable and disable MotionAware zones from Home Assistant and have the state reflected there. Currently this fails with a 400 Bad Request because the resources never load on Bridge Pro.

Changes:

  • Make standard-Bridge-only fields optional (| None = None)
  • Add owner as optional field (present on Bridge Pro)
  • Update get_group() to handle None group

I used a simple Python script to test against a real Hue Bridge Pro and set_enabled() was able to toggle my MotionAware zones.

Related: home-assistant/core#153935, home-assistant/core#160393

A corresponding HA core change will be necessary as the switch platform currently creates toggles from behavior_instance only and has no motion_area_configuration support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant