-
Notifications
You must be signed in to change notification settings - Fork 5
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
No setup function defined error #1
Comments
Sorry for the double post, GitHub gave me a 404 so I thought it didn't submit. Duplicate closed. |
No, it rather looks to me like home assistant can't find the component, because HA complains that it can't find the setup method which should be available automatically as I'm implementing a preconfigured cover entity. |
Hi Cornelius,
Thanks for your reply, I have experience running HA with official integrations but this is the first time I am using a custom component so I might have a few things wrong.
Folder content:
config/custom_components/warema_wms_webcontrol contains:
- __init__.py
- __pycache__ folder, containing __init__.cpython-38.pyc
- cover.py
- manifest.json
Do I need to add anything from your main library?
Configuration:
My config.yaml contains this at root:
warema_wms_webcontrol:
- webcontrol_server_addr:192.168.86.35
Thanks,
Holger
… On 15 Jan 2021, at 17:56, Cornelius Mund ***@***.***> wrote:
No, it rather looks to me like home assistant can't find the component, because HA complains that it can't find the setup method which should be available automatically as I'm implementing a preconfigured cover entity <https://developers.home-assistant.io/docs/core/entity/cover>.
Are you sure you placed the files in the correct folder?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH3AFDGMJ7KGYWKCCLSIWTLS2BXTTANCNFSM4WC3WHBA>.
|
Hi Holger, the problem is with your configuration. The implementation I used it based on the cover platform. Hence you must configure it as such. Try the following:
Best |
Hi Cornelius,
I have now changed the config to exactly the below:
cover:
- platform: warema_wms_webcontrol
webcontrol_server_addr: http://192.168.86.35
update_interval: 300
But now I get this error:
Logger: homeassistant.config
Source: config.py:415
First occurred: 23:31:20 (1 occurrences)
Last logged: 23:31:20
Invalid config for [cover.warema_wms_webcontrol]: [webcontrol_server_addr] is an invalid option for [cover.warema_wms_webcontrol]. Check: cover.warema_wms_webcontrol->webcontrol_server_addr. (See /config/configuration.yaml, line 25).
Thanks,
Holger
… On 16 Jan 2021, at 21:21, Cornelius Mund ***@***.***> wrote:
Hi Holger,
the problem is with your configuration. The implementation I used it based on the cover platform. Hence you must configure it as such. Try the following:
cover:
- platform: warema_wms_webcontrol
webcontrol_server_addr: http://192.168.86.35
update_interval: 300
Best
Cornelius
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AH3AFDFD3F2HH7ZQIBV2THDS2HYMDANCNFSM4WC3WHBA>.
|
I commented out |
Both options are optional so in principle the integration could work even without them. Could you run HA with logging on DEBUG? Maybe that will give us a clue. |
My Webcontrol Pro hub does not seem to create a DNS entry (despite confirming that Can you give me a hint on setting up debugging? Not sure I understand enough to know what we need, Supervisor, OS? Even without parameters, there actually is an error in the logs, but as far as I understand, this is cause by not being able to resolve the standard address: `Log Details (ERROR) Logger: homeassistant.components.cover Error while setting up warema_wms_webcontrol platform for cover During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
This is interesting as it seems like the integration is loading correctly and tries to connect to the default web control address if no options are given. Info on logging for HA can be found here https://www.home-assistant.io/integrations/logger/ |
After installing the integration in custom_components and adding to the root of my config file (using the IP of my Webcontrol) I get this error:
The logs have this error:
Now I am using WebControl Pro, could this be the issue?
The text was updated successfully, but these errors were encountered: