Allow mobile app to disable entities by default#71562
Conversation
|
Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration ( |
|
Not sure if its expected, but when testing this I removed my phone from the integrations page and reloaded the page on my phone |
bdraco
left a comment
There was a problem hiding this comment.
Tested and didn't find any regressions. Verified device registry and entity registry populated as expected.
This is the expected behaviour when sensors haven't been registered (i.e. when config entry has been deleted or when app is first connected). It will trigger this log entry then register the sensor. TBH |
|
I think that it doesn't need to be a warning/error at all as we're returning an error to the mobile app, which can deal with it. |
Breaking change
Proposed change
Add a new optional
default_disabledkeyword to theregister_sensormobile app webhook. This allows the mobile app to indicate which sensors need to be disabled by default.This is a step closer to keeping disabled entities in sync between mobile app / HA.
Also noticed some duplicate logic that I cleaned up.
CC @home-assistant/android @home-assistant/ios-developers
Type of change
Additional information
Checklist
black --fast homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all..coveragerc.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: