eon Labs USB Z-wave (gen5) installation

Free domotica! Forums How can I …? Synology NAS eon Labs USB Z-wave (gen5) installation

This topic contains 22 replies, has 3 voices, and was last updated by  33ced 1 year, 5 months ago.

Viewing 15 posts - 1 through 15 (of 23 total)
  • Author
    Posts
  • #2445

    33ced
    Participant

    bonjour,

    j’ai un NAS synology DS213+, une clé “Aeon Labs USB Z-wave (gen5)” et des capteur figaro acheté dans la boutique ORANGE (détecteur de fumée et d’eau).
    Je n’arrive pas à installé ma clé après avoir installé le service zwave.

    j’ai bien la clé sur le port USB avant :
    DS213> dmesg | grep tty
    [ 0.000000] Kernel command line: root=/dev/md0 rw syno_hw_version=DS213pv10 console=ttyS0,115200 ip=off ihd_num=2 netif_num=1 ip=off initrd=0x2000040,4M
    [ 5.917100] serial8250.0: ttyS0 at MMIO 0xffe04500 (irq = 42) is a 16550A
    [ 5.923806] console [ttyS0] enabled, bootconsole disabled
    [ 5.934811] serial8250.0: ttyS1 at MMIO 0xffe04600 (irq = 42) is a 16550A
    [ 215.927167] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
    DS213>

    ensuite ma clé clignote vert, orange et rouge

    quand je fait un dmesg j’ai ça :
    [ 148.212946] USB Serial support registered for cp210x
    [ 148.218018] usbcore: registered new interface driver cp210x
    [ 148.223601] cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
    [ 163.254553] CIFS VFS: Error connecting to socket. Aborting operation
    [ 163.261050] CIFS VFS: cifs_mount failed w/return code = -113
    [ 169.281893] CIFS VFS: Error connecting to socket. Aborting operation
    [ 169.288360] CIFS VFS: cifs_mount failed w/return code = -113
    [ 175.307237] CIFS VFS: Error connecting to socket. Aborting operation
    [ 175.313705] CIFS VFS: cifs_mount failed w/return code = -113
    [ 214.912879] hub 1-1:1.0: port 2, status 0101, change 0001, 12 Mb/s
    [ 215.119508] usb 1-1.2: new full speed USB device using fsl-ehci and address 4
    [ 215.316252] Got empty serial number. Generate serial number from product.
    [ 215.323291] usb 1-1.2: configuration #1 chosen from 1 choice
    [ 215.885398] PPP generic driver version 2.4.2
    [ 215.918852] cdc_acm 1-1.2:1.0: This device cannot do calls on its own. It is not a modem.
    [ 215.927167] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
    [ 215.932792] usbcore: registered new interface driver cdc_acm
    [ 215.938462] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
    DS213>

    merci d’avance

    #2495
    Mika
    Mika
    Keymaster

    Il y a deja quelques post similaires.

    Avez vous dèjà installer d’autres drivers à tout hasard?

    #2508

    33ced
    Participant

    non je n’ai pas installé d’autre driver. Et puis le driver de la clé ne s’installe pas automatiquement car je n’ai rien fait de spécial?
    Que voyez vous de bizarre dans mon log ? La clé est elle installée et reconnue ?
    merci

    • This reply was modified 1 year, 6 months ago by  33ced.
    #2581

    K.Rens
    Keymaster

    Dans le log du zwave dans pulsestation, vous voyez rien?
    Zwave service, il vous n’offre pas l’option d’utiliser ttyACM0?

    Kind regards,
    K.Rens

    #2620

    33ced
    Participant

    bonsoir je viens de reessayer et ma clé n’est pas reconnu voici le dmesg et le log zwave
    non je ne vois rien

    DS213> dmesg | grep tty
    [ 0.000000] Kernel command line: root=/dev/md0 rw syno_hw_version=DS213pv10 console=ttyS0,115200 ip=off ihd_num=2 netif_num=1 ip=off initrd=0x2000040,4M
    [ 5.916264] serial8250.0: ttyS0 at MMIO 0xffe04500 (irq = 42) is a 16550A
    [ 5.922969] console [ttyS0] enabled, bootconsole disabled
    [ 5.933970] serial8250.0: ttyS1 at MMIO 0xffe04600 (irq = 42) is a 16550A
    [ 43.286060] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
    DS213>

    il n’y a pas de ligne du type « usb 1-1.3: cp210x converter now attached to ttyUSB0 ». ou ttyACM0

    2016-01-25 21:27:02.477 Always, OpenZwave Version 1.3.0 Starting Up
    2016-01-25 21:27:02.477 Info, Setting Up Provided Network Key for Secure Communications
    2016-01-25 21:27:02.478 Warning, Failed – Network Key Not Set
    2016-01-25 21:27:02.478 Info, mgr, Added driver for controller /dev/ttyACM0
    2016-01-25 21:27:02.483 Info, Opening controller /dev/ttyACM0
    2016-01-25 21:27:02.483 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2016-01-25 21:27:02.483 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 2
    2016-01-25 21:27:02.483 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2016-01-25 21:27:02.483 Warning, WARNING: Failed to init the controller (attempt 0)
    2016-01-25 21:27:07.483 Info, Opening controller /dev/ttyACM0
    2016-01-25 21:27:07.483 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2016-01-25 21:27:07.484 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 2
    2016-01-25 21:27:07.484 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2016-01-25 21:27:07.484 Warning, WARNING: Failed to init the controller (attempt 1)
    2016-01-25 21:27:12.484 Info, Opening controller /dev/ttyACM0
    2016-01-25 21:27:12.484 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2016-01-25 21:27:12.484 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 2
    2016-01-25 21:27:12.484 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2016-01-25 21:27:12.484 Warning, WARNING: Failed to init the controller (attempt 2)
    2016-01-25 21:27:17.484 Info, Opening controller /dev/ttyACM0
    2016-01-25 21:27:17.485 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2016-01-25 21:27:17.485 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 2
    2016-01-25 21:27:17.485 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2016-01-25 21:27:17.485 Warning, WARNING: Failed to init the controller (attempt 3)
    2016-01-25 21:27:22.486 Info, Opening controller /dev/ttyACM0
    2016-01-25 21:27:22.486 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2016-01-25 21:27:22.486 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 2
    2016-01-25 21:27:22.486 Error, ERROR: Failed to open serial port /dev/ttyACM0
    2016-01-25 21:27:22.486 Warning, WARNING: Failed to init the controller (attempt 4)
    2016-01-25 21:27:22.486 Detail, contrlr, Notification: DriverFailed
    2016-01-25 21:27:22.486 Warning, WARNING: Tried to write driver config with no home ID set
    2016-01-25 21:27:22.486 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0x00000000

    #2622

    K.Rens
    Keymaster

    [ 43.286060] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
    => Your key is recognized.

    2016-01-25 21:27:22.486 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 2
    => For me this is fixed after a reboot of my synology nas.

    Do not install extra usb drivers or anything, just use the pulsestation package.
    Also: do not yet update to DSM 6.

    • This reply was modified 1 year, 5 months ago by  K.Rens.

    Kind regards,
    K.Rens

    #2626

    33ced
    Participant

    pardon voici mon log zwave directement vu sous ssh de mon sysnology car le log par l’interface pulstation me met un ancien

    2016-02-02 22:48:27.768 Always, OpenZwave Version 1.3.0 Starting Up
    2016-02-02 22:48:27.769 Info, Setting Up Provided Network Key for Secure Communications
    2016-02-02 22:48:27.769 Warning, Failed – Network Key Not Set
    2016-02-02 22:48:27.769 Info, mgr, Added driver for controller /dev/ttyACM0
    2016-02-02 22:48:27.769 Info, Opening controller /dev/ttyACM0
    2016-02-02 22:48:27.770 Info, Trying to open serial port /dev/ttyACM0 (attempt 1)
    2016-02-02 22:48:27.770 Info, Serial port /dev/ttyACM0 opened (attempt 1)
    2016-02-02 22:48:27.771 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
    2016-02-02 22:48:27.771 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
    2016-02-02 22:48:27.771 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
    2016-02-02 22:48:27.771 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
    2016-02-02 22:48:27.771 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
    2016-02-02 22:48:27.771 Detail,
    2016-02-02 22:48:27.771 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) – FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
    2016-02-02 22:48:27.777 Detail, contrlr, Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x33, 0x2e, 0x39, 0x35, 0x00, 0x01, 0x99
    2016-02-02 22:48:27.777 Detail,
    2016-02-02 22:48:27.777 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
    2016-02-02 22:48:27.777 Info, contrlr, Static Controller library, version Z-Wave 3.95
    2016-02-02 22:48:27.777 Detail, Node045, Expected reply was received
    2016-02-02 22:48:27.777 Detail, Node045, Message transaction complete
    2016-02-02 22:48:27.777 Detail,
    2016-02-02 22:48:27.777 Detail, contrlr, Removing current message
    2016-02-02 22:48:27.777 Detail,
    2016-02-02 22:48:27.777 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) – FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
    2016-02-02 22:48:27.781 Detail, contrlr, Received: 0x01, 0x08, 0x01, 0x20, 0xd8, 0xe3, 0x91, 0xef, 0x01, 0x92
    2016-02-02 22:48:27.781 Detail,
    2016-02-02 22:48:27.781 Info, contrlr, Received reply to FUNC_ID_ZW_MEMORY_GET_ID. Home ID = 0xd8e391ef. Our node ID = 1
    2016-02-02 22:48:27.781 Detail, Node227, Expected reply was received
    2016-02-02 22:48:27.781 Detail, Node227, Message transaction complete
    2016-02-02 22:48:27.781 Detail,
    2016-02-02 22:48:27.781 Detail, contrlr, Removing current message
    2016-02-02 22:48:27.781 Detail,
    2016-02-02 22:48:27.781 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) – FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05,
    2016-02-02 22:48:27.785 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x05, 0x28, 0xd7
    2016-02-02 22:48:27.785 Detail,
    2016-02-02 22:48:27.785 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
    2016-02-02 22:48:27.785 Info, contrlr, There is no SUC ID Server (SIS) in this network.
    2016-02-02 22:48:27.785 Info, contrlr, The PC controller is a primary controller.
    2016-02-02 22:48:27.785 Detail, Node215, Expected reply was received
    2016-02-02 22:48:27.785 Detail, Node215, Message transaction complete
    2016-02-02 22:48:27.785 Detail,
    2016-02-02 22:48:27.785 Detail, contrlr, Removing current message
    2016-02-02 22:48:27.785 Detail,
    2016-02-02 22:48:27.785 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) – FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0x
    2016-02-02 22:48:27.789 Detail, contrlr, Received: 0x01, 0x2b, 0x01, 0x07, 0x01, 0x00, 0x00, 0x86, 0x00, 0x01, 0x00, 0x5a, 0xfe, 0x81, 0xff, 0x88, 0x4f, 0x1f, 0x00, 0x0
    2016-02-02 22:48:27.789 Detail,
    2016-02-02 22:48:27.789 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES
    2016-02-02 22:48:27.789 Info, contrlr, Serial API Version: 1.0
    2016-02-02 22:48:27.789 Info, contrlr, Manufacturer ID: 0x0086
    2016-02-02 22:48:27.789 Info, contrlr, Product Type: 0x0001
    2016-02-02 22:48:27.789 Info, contrlr, Product ID: 0x005a
    2016-02-02 22:48:27.789 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
    2016-02-02 22:48:27.790 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
    2016-02-02 22:48:27.790 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
    2016-02-02 22:48:27.790 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
    2016-02-02 22:48:27.790 Detail, Expected reply was received
    2016-02-02 22:48:27.790 Detail, Message transaction complete
    2016-02-02 22:48:27.790 Detail,
    2016-02-02 22:48:27.790 Detail, contrlr, Removing current message
    2016-02-02 22:48:27.790 Detail,
    2016-02-02 22:48:27.790 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) – FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
    2016-02-02 22:48:27.793 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x56, 0x00, 0xac
    2016-02-02 22:48:27.793 Detail,
    2016-02-02 22:48:27.793 Info, contrlr, Received reply to GET_SUC_NODE_ID. Node ID = 0
    2016-02-02 22:48:27.793 Info, Controller Does not Support SUC – Cannot Setup Controller as SUC Node
    2016-02-02 22:48:27.793 Detail, Node172, Expected reply was received
    2016-02-02 22:48:27.793 Detail, Node172, Message transaction complete
    2016-02-02 22:48:27.793 Detail,
    2016-02-02 22:48:27.793 Detail, contrlr, Removing current message
    2016-02-02 22:48:27.793 Detail,
    2016-02-02 22:48:27.793 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x1c) – FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
    2016-02-02 22:48:27.852 Detail, contrlr, Received: 0x01, 0x25, 0x01, 0x1c, 0x01, 0x20, 0xb5, 0xba, 0xf8, 0x8a, 0xfa, 0x68, 0x8d, 0x6a, 0x48, 0x98, 0xf7, 0x82, 0x49, 0x0
    2016-02-02 22:48:27.853 Detail,
    2016-02-02 22:48:27.853 Info, contrlr, Received reply to FUNC_ID_ZW_GET_RANDOM: true
    2016-02-02 22:48:27.853 Detail, Node032, Expected reply was received
    2016-02-02 22:48:27.853 Detail, Node032, Message transaction complete
    2016-02-02 22:48:27.853 Detail,
    2016-02-02 22:48:27.853 Detail, contrlr, Removing current message
    2016-02-02 22:48:27.853 Detail,
    2016-02-02 22:48:27.853 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x02) – FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
    2016-02-02 22:48:27.953 Detail, contrlr, Received: 0x01, 0x25, 0x01, 0x02, 0x05, 0x00, 0x1d, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0
    2016-02-02 22:48:27.953 Detail,
    2016-02-02 22:48:27.953 Info, mgr, Driver with Home ID of 0xd8e391ef is now ready.
    2016-02-02 22:48:27.953 Info,
    2016-02-02 22:48:27.954 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_INIT_DATA:
    2016-02-02 22:48:27.954 Info, contrlr, Node 001 – Known
    2016-02-02 22:48:27.954 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe1 live=1
    2016-02-02 22:48:27.954 Detail, Node001, QueryStage_Probe1
    2016-02-02 22:48:27.954 Detail, Node001, QueryStage_Associations
    2016-02-02 22:48:27.954 Detail, Node001, QueryStage_Neighbors
    2016-02-02 22:48:27.954 Detail, contrlr, Requesting routing info (neighbor list) for Node 1
    2016-02-02 22:48:27.954 Detail, Node001, Queuing (Command) Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00, 0x00, 0x03, 0x7a
    2016-02-02 22:48:27.954 Detail, Node001, Queuing (Query) Query Stage Complete (Neighbors)
    2016-02-02 22:48:27.954 Detail, Expected reply was received
    2016-02-02 22:48:27.954 Detail, Message transaction complete
    2016-02-02 22:48:27.954 Detail,
    2016-02-02 22:48:27.955 Detail, contrlr, Removing current message
    2016-02-02 22:48:27.955 Detail, Node001, Notification: DriverReady
    2016-02-02 22:48:27.956 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 22:48:28.082 Detail, Node001, Notification: NodeAdded
    2016-02-02 22:48:28.083 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 22:48:28.210 Detail, Node001, Notification: NodeProtocolInfo
    2016-02-02 22:48:28.211 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 22:48:28.334 Detail, Node001, Notification: EssentialNodeQueriesComplete
    2016-02-02 22:48:28.335 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 22:48:28.460 Detail, Node001, Notification: ValueAdded
    2016-02-02 22:48:28.461 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 22:48:28.584 Detail, Node001, Notification: NodeNaming
    2016-02-02 22:48:28.585 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 22:48:28.708 Detail,
    2016-02-02 22:48:28.708 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x06) – FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64,
    2016-02-02 22:48:28.716 Detail, contrlr, Received: 0x01, 0x05, 0x01, 0x06, 0x64, 0x0f, 0x96
    2016-02-02 22:48:28.716 Detail,
    2016-02-02 22:48:28.716 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_SET_TIMEOUTS
    2016-02-02 22:48:28.716 Detail, Node015, Expected reply was received
    2016-02-02 22:48:28.716 Detail, Node015, Message transaction complete
    2016-02-02 22:48:28.716 Detail,
    2016-02-02 22:48:28.716 Detail, contrlr, Removing current message
    2016-02-02 22:48:28.716 Detail,
    2016-02-02 22:48:28.716 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x00) – FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x0
    2016-02-02 22:48:28.723 Detail, contrlr, Removing current message
    2016-02-02 22:48:28.724 Detail,
    2016-02-02 22:48:28.724 Info, Node001, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) – Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00,
    2016-02-02 22:48:28.732 Detail, Node001, Received: 0x01, 0x20, 0x01, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x0
    2016-02-02 22:48:28.732 Detail,
    2016-02-02 22:48:28.732 Info, Node001, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
    2016-02-02 22:48:28.732 Info, Node001, Neighbors of this node are:
    2016-02-02 22:48:28.732 Info, Node001, (none reported)
    2016-02-02 22:48:28.732 Detail, Expected reply was received
    2016-02-02 22:48:28.732 Detail, Message transaction complete
    2016-02-02 22:48:28.732 Detail,
    2016-02-02 22:48:28.732 Detail, Node001, Removing current message
    2016-02-02 22:48:28.732 Detail, Node001, Query Stage Complete (Neighbors)
    2016-02-02 22:48:28.732 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
    2016-02-02 22:48:28.732 Detail, Node001, QueryStage_Session
    2016-02-02 22:48:28.733 Detail, Node001, QueryStage_Dynamic
    2016-02-02 22:48:28.733 Detail, Node001, QueryStage_Configuration
    2016-02-02 22:48:28.733 Detail, Node001, QueryStage_Complete
    2016-02-02 22:48:28.733 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
    2016-02-02 22:48:28.733 Warning, CheckCompletedNodeQueries all=1, deadFound=0 sleepingOnly=1
    2016-02-02 22:48:28.733 Info, Node query processing complete.
    2016-02-02 22:48:28.733 Detail, Node001, Notification: NodeQueriesComplete
    2016-02-02 22:48:28.734 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 22:48:28.859 Detail, contrlr, Notification: AllNodesQueried
    2016-02-02 22:48:28.860 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    – OZW_Log.txt 145/145 100%

    #2627

    33ced
    Participant

    oui mais ma clé clignote toujours.
    Faut-il mettre a network-key sous le service zwave de pulsestation et si oui je la trouve ou cette clé?

    je viens de decommenter la ligne < Option name=”NetworkKey” value=”0x01, 0x02,….> du fichier options.xml car j’ai 2016-02-02 22:48:27.769 Warning, Failed – Network Key Not Set, faut-il le faire? Et quelle clé faut-il mettre ?

    merci

    #2628

    33ced
    Participant

    [ 43.286060] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device
    => Your key is recognized.

    2016-01-25 21:27:22.486 Error, ERROR: Cannot open serial port /dev/ttyACM0. Error code 2
    => For me this is fixed after a reboot of my synology nas.

    Do not install extra usb drivers or anything, just use the pulsestation package.
    Also: do not yet update to DSM 6.

    no extra driver and no update dsm 6

    #2629

    33ced
    Participant

    je veux add a device et voici mon log in waiting

    2016-02-02 23:23:53.489 Detail, contrlr, Queuing (Controller) Add Device
    2016-02-02 23:23:53.489 Info, Add Device
    2016-02-02 23:23:53.489 Detail, contrlr, Queuing (Command) ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a, 0x7b
    2016-02-02 23:23:53.489 Detail, Notification: ControllerComand – Starting
    2016-02-02 23:23:53.490 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 23:23:53.618 Detail,
    2016-02-02 23:23:53.618 Info, contrlr, Sending (Command) message (Callback ID=0x0a, Expected Reply=0x4a) – ControllerCommand_AddDevice: 0x01, 0x05, 0x00, 0x4a, 0xc1, 0x0a
    2016-02-02 23:23:53.624 Detail, contrlr, Received: 0x01, 0x07, 0x00, 0x4a, 0x0a, 0x01, 0x00, 0x00, 0xb9
    2016-02-02 23:23:53.624 Detail,
    2016-02-02 23:23:53.625 Info, contrlr, FUNC_ID_ZW_ADD_NODE_TO_NETWORK:
    2016-02-02 23:23:53.625 Info, contrlr, ADD_NODE_STATUS_LEARN_READY
    2016-02-02 23:23:53.625 Detail, Node001, Expected callbackId was received
    2016-02-02 23:23:53.625 Detail, Node001, Expected reply was received
    2016-02-02 23:23:53.625 Detail, Node001, Message transaction complete
    2016-02-02 23:23:53.625 Detail,
    2016-02-02 23:23:53.625 Detail, contrlr, Removing current message
    2016-02-02 23:23:53.625 Detail, Notification: ControllerCommand – Waiting
    2016-02-02 23:23:53.626 Info, mgr, Manager::WriteConfig completed for driver with home ID of 0xd8e391ef
    2016-02-02 23:23:53.882 Info, WriteNextMsg Controller nothing to do

    #2630

    K.Rens
    Keymaster

    Your message of:
    février 3, 2016 at 12:13

    => Great your key is detected and working!

    I do not know why the color changes, but you can try adding a network key.
    It’s always better for security.
    This is an example network key:
    0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x06, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10

    Does your documentation say something about when the key is flashing?

    Kind regards,
    K.Rens

    #2632

    33ced
    Participant

    OK i add the key in zwave service but i don’t add a device, i am in waiting always

    • This reply was modified 1 year, 5 months ago by  33ced.
    • This reply was modified 1 year, 5 months ago by  33ced.
    #2635

    33ced
    Participant

    and my key is blue orange red always

    #2636

    K.Rens
    Keymaster

    You mean you cannot add the device?

    Did you restart the zwave service after filling in the network key?
    It’s needed.
    After the restart, wait 5 minutes or till the log stops adding new lines and then try adding your new device.

    Kind regards,
    K.Rens

    #2637

    33ced
    Participant

    yes i cannot add a fibaro smoke sensor

    I put well “0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x06, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F, 0x10” in network key ?

    already i had restarted the service but i do it yet

Viewing 15 posts - 1 through 15 (of 23 total)

You must be logged in to reply to this topic.