-
-
Notifications
You must be signed in to change notification settings - Fork 28.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add config flow to Netgear LTE #92632
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please split this PR.
It contains a lot of refactoring that can be done in a preliminary or follow-up PR.
from . import CONF_NOTIFY, CONF_RECIPIENT | ||
from .const import DOMAIN |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest that you create const.py in a preliminary PR, with DOMAIN
, CONF_NOTIFY
and CONF_RECIPIENT
.
|
||
from . import CONF_BINARY_SENSOR, CONF_MONITORED_CONDITIONS, DATA_KEY, LTEEntity | ||
from . import LTEEntity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In a preliminary PR you could move this to entity.py
from homeassistant.components.sensor import ( | ||
SensorDeviceClass, | ||
SensorEntity, | ||
SensorEntityDescription, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SensorEntityDescription
could be done in a separate preliminary PR
from homeassistant.components.binary_sensor import BinarySensorEntity | ||
from homeassistant.components.binary_sensor import ( | ||
BinarySensorEntity, | ||
BinarySensorEntityDescription, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think BinarySensorEntityDescription
could be implemented in a separate PR (preliminary or follow-up)
SERVICE_CONNECT_LTE: CONNECT_LTE_SCHEMA, | ||
SERVICE_DISCONNECT_LTE: DISCONNECT_LTE_SCHEMA, | ||
} | ||
hass.data[DATA_HASS_CONFIG] = config |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you should move this under the DOMAIN
key, either as a dict with sub-items or possibly as a dataclass.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This constants resolves to "netgear_lte_hass_config"
. Much will eventually be moved to coordinator and leave just the notify
service using it.
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
…gear_lte_config_flow
Botched commit. Closing to resubmit. |
Breaking change
Netgear LTE can now be set up in the UI. Existing yaml configurations are automatically imported and can be safely removed. The Netgear LTE notify service was previously set up via YAML configuration. This created a service for a specified recipient without having to include the phone number. These services are still available for now. Please adjust any automations or scripts you may have to use the new service and include target for specifying a recipient.
Proposed change
Add config flow to Netgear LTE.
There are a lot of other changes that should be done but have been left out to keep the runtime changes in this PR smaller. I plan on doing followups for the rest.
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
.To help with the load of incoming pull requests: