-
Notifications
You must be signed in to change notification settings - Fork 36
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 module named 'custom_components.zha_toolkit.const' #278
Comments
Thank you for the feedback. This was not released yet and I was not expecting that the project is pulled for using it ;-). I'll be more carefull when adding things to the main branch. This is something that I do not understand about python yet. I've changed the code a bit. |
YW. Actually the following change DOES work very well, as well (after reverting what I've done tonight): diff --git a/custom_components/zha_toolkit/const.py b/custom_components/zha_toolkit/const.py
new file mode 100644
index 0000000..0510443
--- /dev/null
+++ b/custom_components/zha_toolkit/const.py
@@ -0,0 +1 @@
+DOMAIN = "zha_toolkit" Python's not that counterintuitive finally ;-) (at least with And, yes, I pull the main branch regularly. Many thanks for that. PS: Do not change your coding habits, it's easy enough to set a tag and check it out if the main branch becomes 'too wild'. |
Happy to see that this helps with learning about zigbee. I'll leave the code as is - normally I make the updates in dev so updating main is kind of the exception. The changes are to add the config flow so that editing the configuration.yaml can be avoided. Possibly all that remains to be done is to activate it by adding the appropriate https://developers.home-assistant.io/docs/config_entries_config_flow_handler/#updating-the-manifest |
Closing as this is fixed - the const.py file was not under version control. |
Hi,
after a git pull and restart of the component, the initialization failed with the following backtrace:
my workaround was to create the file:
custom_components/zha_toolkit/const/__init__.py
The text was updated successfully, but these errors were encountered: