-
-
Notifications
You must be signed in to change notification settings - Fork 32.6k
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 new integration for AiDot #137504
base: dev
Are you sure you want to change the base?
Add new integration for AiDot #137504
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.
Hi @HongBryan
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
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.
Hi all,
Do I need to modify anything in this current PR? I see that there has been no new news for a long time. What is wrong with this PR? What can I modify so that it can be merged smoothly?
Regards
Two weeks is not a long time with a backlog of over 500 PRs. Just be patient please. |
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 also missing a quality_scale.yaml
file, matching our quality scale and reaching at least bronze
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.
Hello @s1eedz,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:
cd8ba2ad67e19dd9b83c108e0ecd664cd8b71d13
- This commit has something that looks like an email address ([email protected]). Maybe try linking that to GitHub?.
Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:
-
If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.
-
If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.
- If you only made a single commit you should be able to run
(substituting "Author Name" and "
git commit --amend --author="Author Name <[email protected]>"
[email protected]
" for your actual information) to set the authorship information. - If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
- You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
- You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
- Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.
- If you only made a single commit you should be able to run
We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! ❤️
cd8ba2a
to
64532e9
Compare
64532e9
to
477146f
Compare
entry.data[CONF_DEVICE_LIST], | ||
entry.data[CONF_LOGIN_RESPONSE], | ||
entry.data[CONF_PRODUCT_LIST], |
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.
entry.data[CONF_DEVICE_LIST], | |
entry.data[CONF_LOGIN_RESPONSE], | |
entry.data[CONF_PRODUCT_LIST], |
you already pass the entry, you can get it in the corodinator
def discover(dev_id, event: Mapping[str, Any]): | ||
hass.bus.async_fire(dev_id, event) | ||
|
||
try: | ||
await Discover().broadcast_message( | ||
discover, coordinator.login_response[CONF_ID] | ||
) | ||
except OSError as err: | ||
raise ConfigEntryError from err |
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.
move that to _async_setup
in the coordinator
entry.data[CONF_LOGIN_RESPONSE], | ||
entry.data[CONF_PRODUCT_LIST], | ||
) | ||
entry.runtime_data = coordinator |
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.
entry.runtime_data = coordinator | |
await coordinator.async_config_entry_first_refresh() | |
entry.runtime_data = coordinator |
refresh the coordinator once
self.house_list = await self.__login_control.async_get_houses( | ||
self.hass, self.accessToken | ||
) | ||
if self.house_list is None or len(self.house_list) == 0: |
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.
if self.house_list is None or len(self.house_list) == 0: | |
if not self.house_list: |
achieves the same
input_username: str = "" | ||
input_password: str = "" |
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.
input_username: str = "" | |
input_password: str = "" |
input_username = user_input[CONF_USERNAME] | ||
input_password = user_input[CONF_PASSWORD] |
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.
input_username = user_input[CONF_USERNAME] | |
input_password = user_input[CONF_PASSWORD] |
I don't like signle use variables
input_password = user_input[CONF_PASSWORD] | ||
try: | ||
self.login_response = await self.__login_control.async_post_login( | ||
self.hass, |
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.
why do you pass a HomeAssistant object to your lib? That's very likely an indication that's something's off, your lib shouldn't need to know about HA specific objects
vol.Required(CONF_USERNAME, default=input_username): str, | ||
vol.Required(CONF_PASSWORD, default=input_password): str, | ||
} | ||
) |
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.
you can do self.add_suggested_values_to_schema
if you got user input to avoid those variables
try: | ||
# get device_list | ||
device_list: list[ | ||
dict[str, Any] | ||
] = await self.__login_control.async_get_devices( | ||
self.hass, self.accessToken, selected_house[CONF_ID] | ||
) | ||
product_list: list[dict[str, Any]] = [] | ||
if device_list is not None: | ||
# get product_list | ||
productIds = ",".join( | ||
[item[CONF_PRODUCT_ID] for item in device_list] | ||
) | ||
product_list = await self.__login_control.async_get_products( | ||
self.hass, self.accessToken, productIds | ||
) |
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.
don't get those here and store them in the entry. We can get them in the coordinator later
type AidotConfigEntry = ConfigEntry[AidotCoordinator] | ||
|
||
|
||
class AidotCoordinator: |
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.
how are you planning to update your entities? Currently you're not updating anything. The coordinator will need an _async_update
method (except if you're planning to push updates to HA)
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.
We only save the list data here and will not make any updates. We notify HA of device status updates through async_update_ha_state
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 that would mean the light is out of sync with HA if it gets controlled from elsewhere
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.
Are you saying that I need to write a schedule here to retrieve the device list, and once the device list is updated, it will be synchronized to the page in real time. Can I rephrase it so that when the user clicks to reload the module, I can pull down the device list again and synchronize it? If I go to our server regularly to pull the device list, wouldn't it be too wasteful of resources, because the device list usually doesn't change unless a new device is added
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.
no one is talking about real time. The coordinator will automatically poll an endpoint, but we should think how you want to update the state of your devices (not the devices necessarily, but that's also something we do, but not in the first step)
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.
Okay, I will make changes based on your suggestions. Thank you for your suggestion
Breaking change
Proposed change
Type of change
Additional information
Checklist
ruff format 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
.To help with the load of incoming pull requests: