Can’t start zwave network after snapshot

Configuration Z-Wave
1

Hi,

I use ha with a raspberry pi 3a. I installed it on a sd card with getting damaged. So I use a usb stick now and installed ha new. I used a snapshot to get to my last config.
After that I can’t start my zwave network. Under Intergrations - zwave - config I pushed the button start network. But nothing happened.
In my config yaml I integrate it :
zwave: usb_path: /dev/tty/AMA0
Under Supervisor - System - Host System - Hardware, I see `serial:

  • /dev/ttyAMA0
  • /dev/ttyACM0`

The log shows:
Logger: homeassistant.components.zwave
Source: components/zwave/init.py:871
Integration: Z-Wave (documentation, issues)
First occurred: 08:57:48 (4 occurrences)
Last logged: 10:14:39

Z-Wave not ready after 300 seconds, continuing anyway

On the SD card it works perfectly.
Any ideas?

2

When I boot with the SD Card everything works. When I look in the Supervisor - Hardware, one serial port is more then on the USB Stck boot: /dev/ttyS0
Here the OZW Logs:

2020-11-29 12:52:42.144 Always, OpenZwave Version 1.4.3469 Starting Up
2020-11-29 12:53:31.668 Info, Setting Up Provided Network Key for Secure Communications
2020-11-29 12:53:31.669 Warning, Failed - Network Key Not Set
2020-11-29 12:53:31.669 Info, mgr,     Added driver for controller /dev/ttyAMA0
2020-11-29 12:53:31.675 Info,   Opening controller /dev/ttyAMA0
2020-11-29 12:53:31.676 Info, Trying to open serial port /dev/ttyAMA0 (attempt 1)
2020-11-29 12:53:31.682 Info, Serial port /dev/ttyAMA0 opened (attempt 1)
2020-11-29 12:53:31.683 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-11-29 12:53:31.684 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2020-11-29 12:53:31.684 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2020-11-29 12:53:31.684 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2020-11-29 12:53:31.684 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2020-11-29 12:53:31.684 Detail,
2020-11-29 12:53:31.684 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2020-11-29 12:53:31.684 Detail, contrlr, Notification: DriverFailed
3

Don’t use the /dev/AMA0 or /dev/ACM0 instead use /dev/serial/by-id/<whatever>

4

Where can I find the “whatever”?
Here my hardware info:

serial:
  - /dev/ttyAMA0
  - /dev/ttyACM0
  - >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2195893-if00
input: []
disk: []
gpio:
  - gpiochip0
  - gpiochip504
  - gpiochip100
usb:
  - /dev/bus/usb/001/001
  - /dev/bus/usb/001/002
  - /dev/bus/usb/001/003
  - /dev/bus/usb/001/014
  - /dev/bus/usb/001/005
audio:
  '0':
    name: bcm2835_alsa - bcm2835 ALSA
    type: ALSA
    devices:
      - chan_id: '0'
        chan_type: digital audio playback
      - chan_id: '1'
        chan_type: digital audio playback
      - chan_id: '2'
        chan_type: digital audio playback

the “/dev/serial/by-id/” is a other device.

5

Looks like it’s missing.

6

Oh what now? I use the Razberry 2 board when this is important to know.

7

Now it works. I put the following lines in the boot.txt to disable bluetooth and wifi:

dtoverlay=pi3-disable-bt
dtoverlay=pi3-disable-wifi