zwavejs2mqtt unofficial add-on for hassos installs

[johntdyer]

I would love to run zwavejs2mqtt on my HassOS install.

Describe the solution you'd like
The typical approach would be an add-on, and I am hoping for an unoffical add-on repository

Describe alternatives you've considered
n/a

[robertsLando]

I think this is wasy to do by forking the existing addon for the Zwave2Mqtt , are you able to do it?

[blhoward2]

Just a note that you can do so even without an add on. Just install the portainer add on and then install the docker image. It would be good for there to eventually be an add on, though.

[scyto]

the biggest reason to do the add-on is to remove the old addon if zwave2mqtt is to be deprecated, where is the addon located in terms of source (i assume it just pull's roberts container rather than anyone elses) as such can't be too hard to replicate and change - even a no-coder like me might be able to do it....

[scyto]

oh, just read this https://github.com/hassio-addons/addon-zwave2mqtt/issues/70 does that mean even if we created an add-on they wouldn't take it - or just that they don't want to work on it?

[blhoward2]

A lot changed from that post, including the maintainer of qt-openzwave effectively stepping back. There is a proposal to change the path forward to a new server built on the same backend as this project (node-zwave-js).

The people that were working on the integration for ozw are now working on the server.

[scyto]

@blhoward2 thanks, i am happy to use Roberts image for now (runs nicely on my pi with docker) and know how to create my own docker images if it is missing something, i was more trying to give back to community and the code for the add-on isn't really code but mostly docker config - was willing to fork it and attempt to create an add-on... but if folks thinks thats not needed i certainly don't want to push water up hill :-)

[blhoward2]

It wouldn’t hurt for now, actually. I’ve heard no plans to make a Zwavejs2mqtt add on as the integration won’t use that project. Right now it’s difficult for people to install and they need to use Portainer. The timeline on the new integration is months, at least, based on the update posted to the architecture post. An add on would ease installation and it works fine with the MQTT integration.

@robertsLando @AlCalzone Have you heard differently?

[robertsLando]

@frenck Do you know about last news? Could you think about making a new addon now?

[frenck]

I have no time for that at this point, furthermore, things seem to be in early development stages. Happy to jump in at some point, but not now.

[robertsLando]

@frenck Ok no problem. I dunno if you are aware of this but actually we are working with hass team in: https://github.com/zwave-js/zwave-js-server that will be installed in zwavejs2mqtt and will communicate with a new hass addon to create entities (something like the ozw beta integration is doing now with qt-openzwave)

[frenck]

Yes, I'm part of the core team, I'm aware.

[jcam]

Are all of the addons in https://addons.community managed by the core team / @frenck , or could we build out our own and have it added?

Worst case, we just set up our own addon repository that people would need to add via the interface until it becomes 'official'.

As for the timeline @blhoward2 the official integration already supports the switch, sensor, and light class, it is in the dev nightlies, and is being added to quickly. I'd be surprised if we didn't see some sort of beta by February

[frenck]

It is planned for the first Wednesday of February release indeed.

The community add-ons is my private project.

We have discussed it in our team yesterday, an official, core supported and maintained, add-on will me made. One specifically tailored to support the integration.

The Aim, is to have a first version ready to support the first integration version, before the February release.

[robertsLando]

Closing this

[frenck]

WIP: https://github.com/hassio-addons/addon-zwavejs2mqtt

[robertsLando]

Thanks @frenck

[frenck]

No problem @robertsLando! Are you on discord btw?

[robertsLando]

Nope, should I?

[frenck]

No not needed. Will uses issues instead.