-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
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
Fix issues with Point #100843
Fix issues with Point #100843
Conversation
a2f0c9a
to
9507edc
Compare
) | ||
self._device_name = device_name | ||
self._async_unsub_hook_dispatcher_connect = None | ||
self._events = EVENTS[device_name] | ||
self._attr_unique_id = f"point.{device_id}-{device_name}" | ||
self._attr_icon = DEVICES[self._device_name].get("icon") | ||
self._attr_name = f"{self._name} {device_name.capitalize()}" |
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 is set in the super().__init__(
function.
1c431a8
to
5b297e9
Compare
@@ -54,6 +55,7 @@ | |||
{ | |||
vol.Required(CONF_CLIENT_ID): cv.string, | |||
vol.Required(CONF_CLIENT_SECRET): cv.string, | |||
vol.Required(CONF_REDIRECT_URI): cv.string, |
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.
For integrations that connect to devices or services, we no longer accept new YAML configurations or changes.
More information about this can be found in Architecture Decision Record:
Please consider deprecating the yaml configuration as this integration already has a config flow.
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.
Yes I understand that, but I don't feel I have time right now to fix this. My roadmap for the integration is to move configuration to den config-flow.
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.
As written above, we won't accept any yaml configuration changes.
The code is already importing the yaml config to a config entry. Therefore I suggest implementing the changes for the config entry config only.
In another PR, you should only deprecate the yaml 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've removed all references to yaml 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 meant leaving the yaml configuration untouched.
I reviewed it again and saw that the UI-initialized config flow also requires yaml. Therefore, I suggest deprecating the yaml configuration in another PR first, including moving to the new oauth flow.
After the deprecation PR is merged, this bug-fix PR should be small and easy.
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 implement the yaml depreciation here, including the new oauth flow.
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.
Can I get some guidance on how to depricate yaml?
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.
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.
But you want me to split this PR into several?
- Adding a config-flow dialog to allow redirect-uri
- Depricate yaml
- Implement full config-flow (as this pr is doing)
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.
Well it is not possible to authenticate with the current yaml (it requires an uri). Hence we must send more information.
From your message, I assume it has to be one PR.
- Adding a config-flow dialog to allow redirect-uri
- Depricate yaml
- Implement full config-flow (as this pr is doing)
Please make only these changes in this PR and try to keep the PR as small as possible.
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
5b297e9
to
f57d802
Compare
f57d802
to
cad3438
Compare
@@ -54,6 +55,7 @@ | |||
{ | |||
vol.Required(CONF_CLIENT_ID): cv.string, | |||
vol.Required(CONF_CLIENT_SECRET): cv.string, | |||
vol.Required(CONF_REDIRECT_URI): cv.string, |
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 meant leaving the yaml configuration untouched.
I reviewed it again and saw that the UI-initialized config flow also requires yaml. Therefore, I suggest deprecating the yaml configuration in another PR first, including moving to the new oauth flow.
After the deprecation PR is merged, this bug-fix PR should be small and easy.
ed397c2
to
c1985e2
Compare
There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days. |
Proposed change
Fixes authentication issues with Point. Also fixes issues with other minor parts.
Changelog: fredrike/pypoint@v2.3.0...v2.3.2
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: