Andrew Fiddian-Green

@kaikreuzer => ping!

Just to report that this did successfully install 3.2.M2 today (see screenshot below).. 

> might just only want to provide APIs here in core, so the UI knows if an update mechanism is available, and what parameters are used (password, available versions). Then...

> the core should not know anything about package specific upgrade commands. It should only know that there is a script (or class) that can do this and what kind...

An alternative might be to modify the xml schema to allow more than one state element.. ``` ```

@J-N-K I guess this one is in reality not feasible? Or ??

@pgfeller I will start to look at this tomorrow.

If I understand your issue correctly, you are asking for someone to develop an Add-on to integrate things via your API. Or?? If so, then this issue should not be...

@robertsLando you may also want to post something about this on the [OH Community Forum](https://community.openhab.org/) -- for example here... https://community.openhab.org/t/zwave-js-ui-in-place-of-oh-zwave-binding/150007/1

@lsiepel see the forum link in my post above yours