eamonnsullivan commented 2 months ago

The problem

I use docker install and have the latest stable of Home Assistant (2024.7.2) and Z-Wave JS UI (zwave-js-ui: 9.16.0.5ca1c07, zwave-js: 13.0.0). My devices aren't receiving events after the last update yesterday. You can see good events in the Z-Wave UI. For example, an Aeotec TriSensor is reporting that my kitchen is 24.3C, while HA shows it as -4.2C, and the illuminance hasn't updated at all (straight flat line in history) since the upgrade. I tried restarting all of the services, rebooting my Pi, etc., and nothing is happening.

What version of Home Assistant Core has the issue?

core-2024.7.2

What was the last working version of Home Assistant Core?

core-2024.7.2

What type of installation are you running?

Home Assistant Container

Integration causing the issue

zwave_js

Link to integration documentation on our website

https://www.home-assistant.io/integrations/zwave_js

Diagnostics information

config_entry-zwave_js-6e089e068fbcf694ad21af05d5504505.json

home-assistant_zwave_js_2024-07-19T08-12-36.632Z.log

Example YAML snippet

This is a simplified version of my docker compose.

services:
  homeassistant:
    container_name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:stable
    volumes:
      - /media/homeassistant/home_assistant:/config
      - /etc/localtime:/etc/localtime:ro
      - /run/dbus:/run/dbus:ro
      - /media/homeassistant/media:/media
    restart: unless-stopped
    privileged: true
    network_mode: host
    devices:
      - '/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_c625d2963e7ded119b63bc6c4fc49859-if00-port0:/dev/ttyUSB0'
  zwave-js-ui:
    container_name: zwave-js-ui
    image: zwavejs/zwave-js-ui:latest
    restart: unless-stopped
    depends_on:
      - homeassistant
    tty: true
    stop_signal: SIGINT
    environment:
      - SSL_KEY=/etc/letsencrypt/live/sullivanhome.org.uk/privkey.pem
      - SSL_CERTIFICATE=/etc/letsencrypt/live/sullivanhome.org.uk/fullchain.pem
      - SESSION_SECRET=<REDACTED>
      # Uncomment if you want logs time and dates to match your timezone instead of UTC
      # Available at https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
      #- TZ=America/New_York
    networks:
      - zwave
    devices:
      # Do not use /dev/ttyUSBX serial devices, as those mappings can change over time.
      # Instead, use the /dev/serial/by-id/X serial device for your Z-Wave stick.
      - '/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave'
    volumes:
      - ./store:/usr/src/app/store
      - /etc/letsencrypt/live/sullivanhome.org.uk:/etc/letsencrypt/live/sullivanhome.org.uk:ro
      - /etc/letsencrypt/archive/sullivanhome.org.uk:/etc/letsencrypt/archive/sullivanhome.org.uk:ro
    ports:
      - '8091:8091' # port for web interface
      - '3000:3000' # port for Z-Wave JS websocket server
networks:
  zwave:
volumes:
  zwave-config:
    name: zwave-config

Anything in the logs that might be useful for us?

Logger: zwave_js_server.server
Source: components/zwave_js/__init__.py:923
First occurred: 08:49:15 (8 occurrences)
Last logged: 08:52:52

2024-07-19T07:50:48.676Z: 2024-07-19T07:50:48.676Z DRIVER dropping CC with invalid values (Reason: Unsupported scale Lux or corrupted da ta)
2024-07-19T07:51:19.664Z: 2024-07-19T07:51:19.664Z DRIVER dropping CC with invalid values (Reason: Unsupported scale Lux or corrupted da ta)
2024-07-19T07:51:50.502Z: 2024-07-19T07:51:50.502Z DRIVER dropping CC with invalid values (Reason: Unsupported scale Lux or corrupted da ta)
2024-07-19T07:52:21.597Z: 2024-07-19T07:52:21.597Z DRIVER dropping CC with invalid values (Reason: Unsupported scale Lux or corrupted da ta)
2024-07-19T07:52:52.501Z: 2024-07-19T07:52:52.501Z DRIVER dropping CC with invalid values (Reason: Unsupported scale Lux or corrupted da ta)

There's more detail in the logs attached above.

Additional information

Screenshot from 2024-07-19 08-54-21

eamonnsullivan commented 2 months ago

122187 looks similar.

SebastianS0 commented 2 months ago

I have had a similar issue after updating to Z-Wave JS UI to 3.9 (which updates zwave-js/zwave-js-ui to v9.16.0) with the aërQ Temperature & Humidity Sensor I "fixed" it by restoring to 3.8.6. Before restoring I excluded & reset the device but that didn't help

killfreekill commented 2 months ago

Same issue here with Aeotec Multisensor 7. https://github.com/zwave-js/node-zwave-js/discussions/7032

Maybe fixed in 13.0.1 by comming #7031 ? https://github.com/zwave-js/node-zwave-js/pull/7031

eamonnsullivan commented 1 month ago

Yes, I just updated and I think it's working again.