homeassistant-zwave_mqtt icon indicating copy to clipboard operation
homeassistant-zwave_mqtt copied to clipboard

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

Open ghost opened this issue 4 years ago • 18 comments

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?

https://github.com/cgarwood/homeassistant-zwave_mqtt/issues/127#issuecomment-626224621

ghost avatar May 09 '20 20:05 ghost

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

marcelveldt avatar May 10 '20 08:05 marcelveldt

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

mbhoek avatar May 13 '20 09:05 mbhoek

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

marcelveldt avatar May 13 '20 10:05 marcelveldt

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.

Robvred avatar May 19 '20 20:05 Robvred

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.

MartinHjelmare avatar May 19 '20 20:05 MartinHjelmare

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 ?

Robvred avatar May 19 '20 21:05 Robvred

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.

MartinHjelmare avatar May 19 '20 21:05 MartinHjelmare

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

Dinth avatar May 20 '20 16:05 Dinth

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

MartinHjelmare avatar May 20 '20 17:05 MartinHjelmare

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.

Dinth avatar May 21 '20 10:05 Dinth

What does the log say?

MartinHjelmare avatar May 21 '20 11:05 MartinHjelmare

Im not seeing any ozw errors in the log, although the documentation mention "configuration flow" and im not getting any settings at all Screenshot 2020-05-21 at 21 15 31

Dinth avatar May 21 '20 20:05 Dinth

There currently are no settings in the config flow.

MartinHjelmare avatar May 21 '20 21:05 MartinHjelmare

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.

Dinth avatar May 22 '20 07:05 Dinth

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)

floriskruisselbrink avatar May 26 '20 09:05 floriskruisselbrink

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.

MartinHjelmare avatar May 26 '20 10:05 MartinHjelmare

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?

michelcve avatar Jul 18 '20 18:07 michelcve

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

cgarwood avatar Jul 18 '20 21:07 cgarwood