-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
Migrate geniushub to has entity name #126986
base: dev
Are you sure you want to change the base?
Conversation
Hey there @manzanotti, mind taking a look at this pull request as it has been labeled with an integration ( Code owner commandsCode owners of
|
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. |
@joostlek Any idea what the missing test warning is about? It looks like you are testing that line, though I can't be sure. |
At what line is it complaining? Also @zxdavb, maybe you can also help out with testing |
So, I am accessing someone else's system via access token (v1 API). geniushub:
token: !secret genius_token
mac: 00:1a:22:0a:0b:0c First issue:
This is despite the docs saying I can still use yaml: https://www.home-assistant.io/integrations/geniushub/ |
So, configuring via UI, we get... Second issue:
|
... and then:
|
... and then some log warnings that may be caused by me merging back the latest dev branch:
... and:
... and:
... Finally:
|
Let me know if I can help more. |
Was complain that a new line of code wasn't covered by the tests - I think you can ignore this for now. |
Oh lol, I forgot the docs for this one. Good catch: home-assistant/home-assistant.io#36048 |
Okay wait, does the integration work on |
This is what I did:
Is that the answer to your question? Or do you want me to test on the dev branch? Gimme sec... |
OK, on dev, I'm getting:
... and:
|
For teh first: if GH_TYPE in d.data["type"]
KeyError: 'type' I wonder if this is because development of client library has been progressing against device's v3 API (via LAN) and hasn't been tested against v1 API (using token via vendor's webserver). The latter:
is a bit odd... Oh: just a consequence of the first error? |
Proposed change
Migrate geniushub to has entity name. This will add devices and allows the issue sensor names to be translated
@GeoffAtHome can you maybe test this PR and the other PR I opened today?
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: