Let's start talking about the new Z-wave JS integration

Configuration Z-Wave
21

I’m watching this closely and will be doing some demos/videos when appropriate.

2 Likes
22

how long has this been there?

Screen Shot 2021-01-25 at 5.03.32 PM
Screen Shot 2021-01-25 at 5.03.32 PM769×508 81.7 KB

23

About 4 hours ago.

1 Like
24

Heck yes. I’m in as soon as it goes live.

25

I am running zwavejs2mqtt:dev container at the moment.

Is there any form of migration path that can reuse the existing entities created or is it start again (i don’t mind the answer, just want to be clear before i start moving over and testing).

If i start again i assume it is just a matter of removing the mqtt config from my configuration.yaml, deleting the devices/entities, turn of hass discovery in zwavejsmqtt and then install the new integration when available?

26

No migration is planned from zwave or ozw to zwavejs2mqtt

There’s a decent chance of a migration path from zwave and/or ozw to the new zwave_js component - that’s not the same as zwavejs2mqtt

27

thanks, i assume my ‘migration’ steps look roughly right?

28

Can we gather some ‘ideal’ settings? Here’s mine at the moment… They work pretty well but I’m not set on the naming yet.

zwavejs
zwavejs1915×887 127 KB

29

Those settings are for MQTT. For the Z-Wave JS integration they would not be necessary.

30

If you would like to use zwavejs2mqtt as the server for the Z-Wave JS integration, you can turn on the WS Server in the settings (might only be in dev builds, if using docker be sure to publish the WS port). You can even turn off MQTT if you don’t need it. Since HA doesn’t yet have control panel capabilities, this works well in the meantime.

image
image756×817 39.1 KB

2 Likes
31

It must be. I just updated to the latest (non-dev) image and it’s not there.

32

It’s available since 1.0.0-rc.0.

33

apparently the latest Docker image only contains the “beta” version of that build?

ex2

34

If you’re referring to the latest docker tag, then maybe? There is a 1.0.0-rc.1 tag and dev tag, both should work.

You’ll still need to install the dev version of HA to use it.

35

yup.

I’m not sure what the “latest” docker image build cycle is but I don’t see the benefit right now to try to build my own image from the latest release in the repo.

It’s way too early to put that much effort into it right now.

36

You don’t have to build anything, just pull the dev or rc tags instead of latest.

37

I was just going by this:

ex
ex1059×153 9.58 KB

from here

I went to the Docker Hub and didn’t see any other releases there and it redirected you back to the github repo above.

38

There are probably over a hundred builds on docker hub. It looks like there are builds for maybe every commit. As I said before, you can use the dev or 1.0.0-rc.1 tags.

The dev tag is the second one in the list. You can use the Filter to search for other tags.

image
image1089×1050 91.2 KB

1 Like
39

it’s definitely in the dev tag, i upgraded from :latest to :dev
here is my docker-compose

version: '3.7'
services:
  zwavejs2mqtt:
    container_name: zwavejs2mqtt
    image: zwavejs/zwavejs2mqtt:dev
    restart: always
    tty: true
    stop_signal: SIGINT
    networks:
      - zwave
    devices:
      - '/dev/ttyAMA0:/dev/ttyAMA0'
    volumes:
      - ./store:/usr/src/app/store
    ports:
      - '80:8091'
      - '3000:3000' 

networks:
  zwave:
# volumes:
#   zwavejs2mqtt:
#     name: zwavejs2mqtt
2 Likes
40

doh! :man_facepalming:

nevermind.

I saw this:

ex

and never clicked the tag header.

I’m an idiot sometimes.

Thanks for pointing that out. :laughing:

EDIT:

done…