Domoticz on OpenWRT

Compatibility (hardware, devices and OS)
HM31
Posts: 8
Joined: Friday 04 August 2017 16:13
Target OS: NAS (Synology & others)
Domoticz version:
Contact:

Re: Domoticz on OpenWRT

Post by HM31 » Wednesday 30 August 2017 14:55

Plugged Aeon Labs Aeotec Z-Wave Z-Stick (ZW090). Seems to be recognized by Omega2+ by adding /dev/ttyACM0 but can't add it in Domoticz Hardware. Log says "Openzwave driver failed!".

Any suggestion to track where the issue is (Onion Omega2+ is based on LEDE OS)?

HM31
Posts: 8
Joined: Friday 04 August 2017 16:13
Target OS: NAS (Synology & others)
Domoticz version:
Contact:

Re: Domoticz on OpenWRT

Post by HM31 » Thursday 07 September 2017 3:17

Here is in more details what I get :
1. plugin ZW090 usb stick :
OS recognize the USB device

Code: Select all

[ 3090.322796] usb 2-1: new full-speed USB device number 2 using ohci-platform
[ 3090.546582] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
2. Adding hardware in
Image
3. Domoticz log :

Code: Select all

 2017-09-06 19:59:00.044 Domoticz V3.8153 (c)2012-2016 GizMoCuz
2017-09-06 19:59:00.046 Build Hash: b97777b, Date: 2016-11-09 06:33:42
2017-09-06 19:59:00.049 Startup Path: /usr/bin/
2017-09-06 19:59:00.942 Active notification Subsystems: gcm, http (2/12)
2017-09-06 19:59:01.056 WebServer(HTTP) started on address: :: with port 8080
2017-09-06 19:59:01.101 Proxymanager started.
2017-09-06 19:59:01.267 Starting shared server on: :::6144
2017-09-06 19:59:01.271 TCPServer: shared server started...
2017-09-06 19:59:01.273 RxQueue: queue worker started...
2017-09-06 19:59:03.628 EventSystem: reset all events...
2017-09-06 19:59:03.631 EventSystem: reset all device statuses...
2017-09-06 19:59:03.646 EventSystem: Started
2017-09-06 20:48:04.660 Incoming connection from: 192.168.2.219
2017-09-06 20:50:45.078 OpenZWave: using config in: /usr/share/domoticz/openzwave/
2017-09-06 20:50:45.153 OpenZWave: Starting...
2017-09-06 20:50:45.154 OpenZWave: Version: 1.4-164-g770378b
2017-09-06 20:51:05.249 Error: OpenZWave: Driver Failed!! 
4. lsusb informations :

Code: Select all

[email protected]:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0658:0200 Sigma Designs, Inc.
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Code: Select all

[email protected]:~# lsusb -s2:2 -v

Bus 002 Device 002: ID 0658:0200 Sigma Designs, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0         8
  idVendor           0x0658 Sigma Designs, Inc.
  idProduct          0x0200
  bcdDevice            0.00
  iManufacturer           0
  iProduct                0
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           67
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      2 Abstract (modem)
      bInterfaceProtocol      1 AT-commands (v.25ter)
      iInterface              0
      CDC Header:
        bcdCDC               1.10
      CDC Call Management:
        bmCapabilities       0x00
        bDataInterface          1
      CDC ACM:
        bmCapabilities       0x00
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0020  1x 32 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
I did an opkg install openzwave but changed nothing.

irimi
Posts: 41
Joined: Saturday 03 January 2015 14:09
Target OS: Raspberry Pi
Domoticz version: V3.5877
Location: Germany
Contact:

Re: Domoticz on OpenWRT

Post by irimi » Wednesday 27 September 2017 21:55

Hi timeless,

I'm trying to compile domoticz on recent lede trunk, but I get following error:

Code: Select all

CMake Error at [...]/lede/source/staging_dir/host/share/cmake-3.8/Modules/FindBoost.cmake:1842 (message):
  Unable to find the requested Boost libraries.

  Boost version: 1.65.1

  Boost include path:
  [...]/lede/source/staging_dir/target-arm_arm1176jzf-s+vfp_musl_eabi/usr/include


  Could not find the following Boost libraries:

          boost_thread
          boost_date_time
          boost_system

  No Boost libraries were found.  You may need to set BOOST_LIBRARYDIR to the
  directory containing Boost libraries or BOOST_ROOT to the location of
I guess the reason is above include path because the correct path of boost 1.65.1 is in a subdir boost !?

Code: Select all

  [...]/lede/source/staging_dir/target-arm_arm1176jzf-s+vfp_musl_eabi/usr/include/boost
But I can't see how to update the lede/Makefile correctly ?
lede domoticz package Makefile version is:

Code: Select all

PKG_NAME:=domoticz
PKG_VERSION_MAJOR:=3
PKG_VERSION_PATCH:=8153
PKG_VERSION:=$(PKG_VERSION_MAJOR).$(PKG_VERSION_PATCH)
PKG_RELEASE:=3

Kruu
Posts: 14
Joined: Tuesday 17 January 2017 21:27
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Domoticz on OpenWRT

Post by Kruu » Tuesday 17 October 2017 19:36

HM31 wrote:
Wednesday 30 August 2017 14:55
Plugged Aeon Labs Aeotec Z-Wave Z-Stick (ZW090). Seems to be recognized by Omega2+ by adding /dev/ttyACM0 but can't add it in Domoticz Hardware. Log says "Openzwave driver failed!".

Any suggestion to track where the issue is (Onion Omega2+ is based on LEDE OS)?
Have you figure this one out?

kofec
Posts: 8
Joined: Friday 16 September 2016 14:16
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Domoticz on OpenWRT

Post by kofec » Thursday 19 October 2017 11:42

Regarding your issue - maybe it is matter of rights for /dev/ttyACM0. I had simiar issue with MySensors conected via serial port.
Or change to run domoticz as root or:
chmod 777 /dev/ttyACM0

kofec
Posts: 8
Joined: Friday 16 September 2016 14:16
Target OS: Raspberry Pi
Domoticz version:
Contact:

Re: Domoticz on OpenWRT

Post by kofec » Thursday 19 October 2017 20:50

Hi, Regarding issue with Boost library. I tried "amke clean" and many other option (like diffconf etc). The only way was to clean clone git repository and choose platform and packets from beginning. I have to also choose python3 as module and boost python as module.

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests