How to proceed with testing now that this component is part of core?

[ghost]

As mentioned by marcelveldt development on this component in this repository has ceased has been moved to homeassistant core. So how do those of us who are interested in continuing to test the development this component do so? Is there going to be a specialized github branch, or soon will this be introduced into a stable release?

#127 (comment)

[marcelveldt]

This will be introduced in Home Assistant beta so feel free to continue testing there!

[mbhoek]

Does it make sense to put a notice in the README.md and/or archive this repository?

[marcelveldt]

We're still moving code. Once done this repo will be archived.
At this time our project documentation lives here ;-)

[Robvred]

So that means if we didn't use an home assistant beta version, we will have no more update in this repo ?
Because I was thinking to continue to use this module via HACS and my home assistant stable version.

[MartinHjelmare]

The new integration will be included in 0.110.0 that goes out tomorrow. There are three platforms that are present here in the custom integration that are not included in 0.110.0:

• climate
• cover
• fan

We're working on adding these too. You can help by adding device mqtt dumps of your devices that we don't yet have data on. We're particularly interested in fan devices.

[Robvred]

Thanks @MartinHjelmare, Unfortunately I didn't have any fan, but I've just prepare an mqtt dump for covers with the garage door.
So tomorrow ;) if we use an stable version of HomeAssistant via Docker, the module will be add too, and we will have to remove our HACS extension isn't ?

[MartinHjelmare]

You can still keep using the custom integration if you so wish. We just won't be updating it.

Side note: We have renamed the integration in 0.110.0 to ozw.

[Dinth]

@MartinHjelmare is there any procedure for upgrading from this to built in component?

[MartinHjelmare]

It should work to remove the custom integration from integrations menu and then add the builtin integration from the integrations menu.

[Dinth]

I did so. After adding OpenZwave (beta) integration, im getting a dialog saying to confirm setup (although theres nothing to confirm as the dialog is empty) and after conifrming the integration is added but doesnt pick up any devices/entities.

[MartinHjelmare]

What does the log say?

[Dinth]

Im not seeing any ozw errors in the log, although the documentation mention "configuration flow" and im not getting any settings at all

[MartinHjelmare]

There currently are no settings in the config flow.

[Dinth]

I had no error messages from ozw at all. I've been trying to to enable debug on the integration, in the mean time readded the integration a couple of times and finally it has picked up.

[floriskruisselbrink]

The 'Confirm set up' window doesn't appear for me when I want to add the ozw component. I am using the custom component from this repo via hacs for the last few weeks just fine.

Upgraded HA to 0.110.2, and when I try to install the OpenZWave (beta) integration, the 'confirm set up' window does not appear, instead I'm being redirected back to the list of all possible integrations to add. Meanwhile in the home-assistant log this appears:

2020-05-26 11:38:46 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration ozw: cannot import name 'OZW_READY_STATES' from 'openzwavemqtt.const' (/usr/local/lib/python3.7/site-packages/openzwavemqtt/const.py)

[MartinHjelmare]

Have you removed all traces of the custom integration before adding the new integration? I would guess that there's an older version of the openzwavemqtt package still installed.

[michelcve]

What's the current status? I'm still on the beta from this repo, and a bit reluctant to switch to the 'official' one...

As I understand from this thread, 'climate', 'cover' and 'fan' are not supported in the official one, and some people have trouble migrating...? Is that still true?

[cgarwood]

@michelcve all platforms are now in the official/code component