Error: Z-Wave JS Retrying setup: Z-Wave JS Server version is incompatible: {0} a version is required that supports at least api schema {1}

Configuration Z-Wave
6

You need to re-add the community repo for your addons.

1 Like
7

i think so but no idea where to get it …
i tried

but doesnt work

8

this one also doesnt work

9

https://addons.community/#installation

1 Like
10

thank you!

1 Like
12

I’m seeing the same issue. I’m running " Home Assistant Core 2022.6.2". On another host I run jwavejs2mqtt in docker-compose, version “zwavejs2mqtt: 6.9.1, zwave-js: 9.2.2”. 6.9.1 is the “latest” release according to Releases · zwave-js/zwavejs2mqtt · GitHub

13

Not sure where you’re seeing that 6.9.1 is the latest? 6.11.0 has been out for 10 days, 6.10 before that for 13 days.

image
image722×391 18.7 KB

14

sudo docker-compose pull && sudo docker-compose up -d to update your container.

15

Thank you! I missed the docker-compose up -d step. I did that and now it’s working fine.

2 Likes
16

Hi @firstof9,

Thank you for your responses!
Can you tell if re-assing the Z-wave JS repo will reset all added Z-wave devices so that they will need to be re-added as well? This of course would be quite unfortunate given the number of devices one may have configured…

17

Why would it reset the devices?

18

@firstof9, what I wrote could be misunderstood. I did not mean resetting actual devices. I meant to ask if there is a danger of z-wave devices to disappear in Home Assistant so that they will need to be re-added.

19

Only if you’ve hard reset your zwave stick.

1 Like
20

@all The original issue is resolved by first removing the Z-wave addon and integrations and reinstalling them.

A side effect of this procedure is that all automations missed trigger, condition and action references. An automation like that would display “unknown action” for action. In YAML format I can see type, device_id, entity_id and domain properties defined. The automation would no work however. @firstof9 It looks like entity_id values have changed after re-installation and healing. Is this to be expected? What can be other reasons?

21

Yes because you nuked the integration thus, nuking all the entities.

Your “solution” isn’t the correct one, all you needed to do was update the addon, never remove the integration.

22

I did try to update by bumping up the version - when new version came, but that didn’t resolve the original problem. I did also try re-installing ONLY the addon - didn’t help. I restarted Home Assistant after that - didn’t help. This is the reason I opted for re-installation of the integration in addition. When that is said, may be I did the “update” incorrectly. Rookie period… jumped over to Home Assistant this year :slight_smile: How would I do an update properly?

23

Only by updating the addon, if for some odd reason that doesn’t work, head over to discord for some realtime troubleshooting/assistance.

1 Like
24

Not sure if this is the correct place for a possible solution as I use ansible to manage my containers. This includes Home Assistant, Zigbee and zWave, in my zWave task all I have to do is update the dependency version for zwave

---
- name: Check if zwave rule exists
  stat:
    path: "/etc/udev/rules.d/50-zwave-symlink.rules"
  register: zwave_rule

- name: Create zwave rule if required
  copy:
    src: 50-zwave-symlink.rules
    dest: /etc/udev/rules.d/50-zwave-symlink.rules
    owner: root
    group: root
    mode: '0644'
  when: not zwave_rule.stat.exists

- name: Restart udev
  command: "udevadm control --reload-rules"
  when: not zwave_rule.stat.exists

- name: Docker service - zWave to MQTT
  docker_container:
    name: zwave
    hostname: "zwave"
    networks:
      - name: "{{ network_name }}"
    restart_policy: unless-stopped
    image: "zwavejs/zwavejs2mqtt:7.0.0"
    exposed_ports:
      - 8091
    published_ports:
      - 3000:3000
    devices:
      - "/dev/serial/by-id/usb-0658_0200-if00:/dev/ttyZWAVE"
    volumes:
      - "/data/zwavejs2mqtt/store:/usr/src/app/store"
      - "/etc/resolv.conf:/etc/resolv.conf"
    env:
      TZ: "Europe/Berlin"
      ZWAVEJS_EXTERNAL_CONFIG: "/usr/src/app/store/.config-db"
    labels:
      traefik.enable: "true"
      traefik.http.routers.zwave.rule: Host("zwave.{{ domain }}")
      traefik.http.routers.zwave.tls: "true"
      traefik.http.routers.zwave.entrypoints: websecure
      traefik.http.services.zwave.loadbalancer.server.port: "8091"
    state: started
...

Witht the home assistant task being:

---
- name: Docker service - homeassistant
  docker_container:
    name: homeassistant
    hostname: "homeassistant"
    networks:
      - name: "{{ network_name }}"
    restart_policy: unless-stopped
    image: "homeassistant/home-assistant:2022.8"
    exposed_ports:
      - 8123
    volumes:
      - "/data/homeassistant/config:/config"
      - "/etc/localtime:/etc/localtime"
    env:
      TZ: "Europe/Berlin"
    labels:
      traefik.enable: "true"
      traefik.http.routers.homeassistant.rule: Host("homeassistant.{{ domain }}")
      traefik.http.routers.homeassistant.tls: "true"
      traefik.http.routers.homeassistant.entrypoints: websecure
    state: started
...
25

Sorry, missed the rules file: 50-zwave-symlink.rules

$ cat 50-zwave-symlink.rules 
SUBSYSTEM=="tty", ATTRS{idVendor}=="0658", ATTRS{idProduct}=="0200", SYMLINK+="ttyZWAVE"
26