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
Disable creating port mappings from UI, add discovery from component #18565
Conversation
Please do not merge. I'm not happy with the state of the flow. |
Please add |
@dgomes Please review. Any comment is welcome. The component has been rewritten to use the |
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.
LGTM!
I think that we need to login to Lokalise to remove the no longer needed translation keys. Just removing the files won't help as they are not the source of truth. |
I don't get what you're trying to say. I removed the files as these were:
|
Changing the translation files has no effect at all. We just run |
And because the are no longer up to date because you changed the keys, you have to log in to Lokalise and update them there |
Ok, thank you for explaining. I've joined the backend project. It seems that I cannot change any keys in Localise. |
Wrong button... |
@StevenLooman you need to remove the translations from the PR in order for this PR to be merged |
Done! |
Minor fix to |
@StevenLooman make sure you remove the commits that remove the translation files |
Can we restart travis? @dgomes |
Restarted the job. |
This PR now removes translations instead of not changing them in this PR. |
460ed89
to
ca9b1e6
Compare
I must have mis-read @dgomes' comment. I can only remove the commit which deleted the translations, not which altered them as it contains more changes. Is this mergable now? |
4fbe059
to
4a06064
Compare
I've re-applied all the changes. No translations are touched. |
Anything I can do? |
(DOMAIN_UPNP, self.unique_id) | ||
}, | ||
'name': self.name, | ||
'via_hub': (DOMAIN_UPNP, self._device.udn), |
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 see that you register a via_hub here but that device is not created anywhere ?
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.
It is created in the upnp
component itself
8426a51
to
65d9709
Compare
Thanks! |
…ome-assistant#18565) * Disable creating port mappings from UI, add discovery from component * Remove unused constant * Upgrade to async_upnp_client==0.13.6 and use manufacturer from device * Upgrade to async_upnp_client==0.13.7
Description:
Disable creating port mappings from UI (see #17937)
Add discovery from component (see #17400)
Upgrade to
async_upnp_client==0.13.3
to support async discoveryPossible fix for #18066: SSL being required when talking to non-SSL-enabled services
Related issue (if applicable):
fixes #17937, fixes #17400
Pull request in home-assistant.io with documentation (if applicable): -
Checklist:
tox
. Your PR cannot be merged unless tests passIf user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
REQUIREMENTS
variable (example).requirements_all.txt
by runningscript/gen_requirements_all.py
..coveragerc
.