-
-
Notifications
You must be signed in to change notification settings - Fork 32.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
HA fails to start with custom version of existing component #21579
Comments
How does your zwave folder in custom components look? |
That looks alright. Your logs don't show any error nor have any mention of zwave. You copied wrong part? |
@balloob HA seems to get stuck right there when all the files are copied over. There are no errors at all that I can see even after setting the logger level to debug. When trying to access the HA through the browser I can't connect. If I only copy |
what kind of errors? |
@balloob If I copy only
If I copy all the zwave files, I get no errors but HA won't start at all. Here are the full logs from start to where it gets stuck: https://hastebin.com/ejohinodip.cs |
So when you're copying the files, are you copying the files from 0.88.2 or from dev ? |
I downloaded the zip file of the release and then copied it over @balloob that's been my standard workflow whenever I updated HA and put back the custom code. |
@balloob I just tried this with lifx, and rainmachine components as "custom_components" and they worked just fine so something with zwave specifically is causing some issues. Could it have to do with |
Nah, it's complaining about config_flow because you didn't copy that. Can you try updating these lines to be relative:
To make relative: |
i made the changes to those files and same issue:
|
@balloob just tried this on a brand new install and I got the same issue. |
Steps I did on the new install:
|
Added a PR to fix the relative imports. I am unable to reproduce it locally, but then I also don't have a Z-Wave stick to test with. So I am just running until it hits |
Thanks @balloob I'll test it as soon as it's in. |
I know it hasn't been too long since you last posted but... Is this still an issue you are experiencing? Can you please try upgrading to the latest version of Home Assistant (0.90) and report back if this is still a problem? Thanks! |
Will double check this this weekend and report back.
…On Thu, Mar 21, 2019 at 8:21 PM beatified ***@***.***> wrote:
I know it hasn't been too long since you last posted but...
Is this still an issue you are experiencing? Can you please try upgrading
to the latest version of Home Assistant (0.90) and report back if this is
still a problem? Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#21579 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABATkOAFgxqbwaN0q1SEH7IgMWqaM2LJks5vZCINgaJpZM4baJjy>
.
|
So I rechecked with the latest version I have a
Here is the error:
|
Also, this error shows up once you load the frontend so you won't see anything in the logs if you just start the service. but once you load the frontend this error shows up. |
Change this line: To: assert module is not None, component |
So that you can see which one failed. |
Feel free to put that in a PR too, would be good to know for future reports too. |
@balloob here is the result: |
Ah I know what's going on. We add config sections to PR welcome again 👍 |
And that PR would fix this issue. |
Home Assistant release with the issue:
0.88.2
Operating environment (Hass.io/Docker/Windows/etc.):
Debian 9
Component/platform:
https://www.home-assistant.io/components/zwave/
Description of problem:
HA fails to start when customizing an existing component. With Logger set to Debug no errors are printed to the logs. See traceback section for where it gets stuck.
Problem-relevant
configuration.yaml
entries and (fill out even if it seems unimportant):I'm using the Zwave Integration and not using the YAML in configuration.yaml
Traceback (if applicable):
Additional information:
I copied over all the files from from the
components/zwave
directory intocustom_components/zwave
, changedconst.py
andnode_entity.py
to fire a new event. This has worked just fine before the re-org of the codebase. The changes i'm making to those two files are in this PR that we decided not to merge: #10865. To reiterate, this worked before the code re-org and i will try other components to see if they exhibit the same issue.The text was updated successfully, but these errors were encountered: