Availability of new Z-Wave commands.

145 views
Skip to first unread message

Tehnoinstyle Aleksey

unread,
Aug 27, 2016, 4:11:26 PM8/27/16
to OpenRemote
Hi Rainer Hitz.

I want to try to upgrade from 2.1.1 to 2.5.0.
What is the current version at the moment? Now I have: OpenRemote Z-Wave protocol version : '2.0.1'

I see by the posts, that is: OpenRemote Z-Wave protocol version : '3.0.0' It added new classes of commands to the thermostat?

Thanks.

Rainer Hitz

unread,
Aug 31, 2016, 3:45:26 AM8/31/16
to OpenRemote
The current version is '3.0.0'.

Z-Wave 3.0.0 supports the following Z-Wave command classes:

COMMAND_CLASS_THERMOSTAT_SETPOINT

STATUS_SETPOINT_TYPE_HEATING_SCALE_CELSIUS
STATUS_SETPOINT_TYPE_HEATING_SCALE_CELSIUS_TARGET

SET_SETPOINT_TYPE_HEATING_SCALE_CELSIUS
SET_SETPOINT_TYPE_HEATING_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_COOLING_SCALE_CELSIUS
SET_SETPOINT_TYPE_COOLING_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_FURNACE_SCALE_CELSIUS
SET_SETPOINT_TYPE_FURNACE_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_DRY_AIR_SCALE_CELSIUS
SET_SETPOINT_TYPE_DRY_AIR_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_MOIST_AIR_SCALE_CELSIUS
SET_SETPOINT_TYPE_MOIST_AIR_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_AUTO_CHANGEOVER_SCALE_CELSIUS
SET_SETPOINT_TYPE_AUTO_CHANGEOVER_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_ENERGY_SAVE_HEATING_SCALE_CELSIUS
SET_SETPOINT_TYPE_ENERGY_SAVE_HEATING_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_ENERGY_SAVE_COOLING_SCALE_CELSIUS
SET_SETPOINT_TYPE_ENERGY_SAVE_COOLING_SCALE_FAHRENHEIT
SET_SETPOINT_TYPE_AWAY_HEATING_SCALE_CELSIUS
SET_SETPOINT_TYPE_AWAY_HEATING_SCALE_FAHRENHEIT


COMMAND_CLASS_THERMOSTAT_FAN_MODE

STATUS_THERMOSTAT_FAN_MODE

SET_THERMOSTAT_FAN_MODE_LOW
SET_THERMOSTAT_FAN_MODE_AUTO_LOW
SET_THERMOSTAT_FAN_MODE_HIGH
SET_THERMOSTAT_FAN_MODE_AUTO_HIGH
SET_THERMOSTAT_FAN_MODE_MEDIUM
SET_THERMOSTAT_FAN_MODE_AUTO_MEDIUM
SET_THERMOSTAT_FAN_MODE_CIRCULATION
SET_THERMOSTAT_FAN_MODE_HUMIDITY
SET_THERMOSTAT_FAN_MODE_LEFT_RIGHT
SET_THERMOSTAT_FAN_MODE_UP_DOWN
SET_THERMOSTAT_FAN_MODE_QUIET


COMMAND_CLASS_THERMOSTAT_FAN_STATE

STATUS_THERMOSTAT_FAN_STATE


COMMAND_CLASS_THERMOSTAT_MODE

STATUS_THERMOSTAT_MODE

SET_THERMOSTAT_MODE_OFF
SET_THERMOSTAT_MODE_HEAT
SET_THERMOSTAT_MODE_COOL
SET_THERMOSTAT_MODE_AUTO
SET_THERMOSTAT_MODE_AUXILIARY_HEAT
SET_THERMOSTAT_MODE_RESUME
SET_THERMOSTAT_MODE_FAN_ONLY
SET_THERMOSTAT_MODE_FURNACE
SET_THERMOSTAT_MODE_DRY_AIR
SET_THERMOSTAT_MODE_MOIST_AIR
SET_THERMOSTAT_MODE_AUTO_CHANGEOVER
SET_THERMOSTAT_MODE_ENERGY_SAVE_HEAT
SET_THERMOSTAT_MODE_ENERGY_SAVE_COOL
SET_THERMOSTAT_MODE_AWAY
SET_THERMOSTAT_MODE_FULL_POWER


COMMAND_CLASS_THERMOSTAT_OPERATING_STATE

STATUS_THERMOSTAT_OPERATING_STATE


The themostat command classes have been tested with the 'Danfoss Radiator Thermostat LC13 Living Connect' and the 'Radio Thermostat Company of America CT100'.

Tehnoinstyle Aleksey

unread,
Aug 31, 2016, 9:41:55 AM8/31/16
to OpenRemote
Oh, very, very good!

In the coming days I will try to update OpenRemote to 2.1.1 (on my Synology NAS) to version 2.6.2 and check my thermostats.

And where i can now download the version `3.0.0` ? On the old site, for "free design" where - to download a zwave.jar file?  Or, the zwave.jar file is now located directly in the controller 2.6?


Many thanks.

среда, 31 августа 2016 г., 10:45:26 UTC+3 пользователь Rainer Hitz написал:
or.png

Rainer Hitz

unread,
Sep 2, 2016, 2:56:22 AM9/2/16
to OpenRemote
OpenRemote Controller 2.5 and 2.6 (Beta 1) contains the Z-Wave version 3.0.0 - no need to download a separate zwave.jar.

Tehnoinstyle Aleksey

unread,
Sep 3, 2016, 11:04:20 AM9/3/16
to OpenRemote
I updated the controller 2.1.1 to 2.6.2. Everything is working normally, and even the rules. But it is not working Z-Wave protocol. In folder

/volume1/@appstore/OpenRemote/webapps/controller/WEB-INF/lib

i not see folder /native and file RXTXcomm-2.2-pre2.jar

In zwave.log:
--------------------------------------------------------------------

  OpenRemote Z-Wave protocol version : '3.0.0'

--------------------------------------------------------------------

DEBUG 2016-09-03 17:48:38,953 (Z-Wave): Connection_Manager          : Adding shutdown hook to manage unclosed Z-Wave connections in case of controller exit.
INFO 2016-09-03 17:48:39,060 (Z-Wave):  Serial_Port                 : Opening the serial port [COM port: /dev/ttyUSB0, Communication Layer: RXTX]...
ERROR 2016-09-03 17:48:39,163 (Z-Wave): Serial_Port_RXTX            : Failed to configure the serial port [Name: '/dev/ttyUSB0', Communication Layer: RXTX] because it does not exist.
ERROR 2016-09-03 17:48:39,165 (Z-Wave): Serial_Port                 : Failed to open the serial port [COM port: /dev/ttyUSB0, Communication Layer: RXTX].


In boot.log
Введите код...org.openremote.controller.exception.NoSuchCommandException: The node '1' is not known by the Z-Wave controller
at org.openremote.controller.protocol.zwave.ZWaveCommandBuilder.build(ZWaveCommandBuilder.java:212)
at org.openremote.controller.command.CommandFactory.getCommand(CommandFactory.java:164)
at org.openremote.controller.model.xml.Version20SensorBuilder.parseSensorEventProducer(Version20SensorBuilder.java:423)
at org.openremote.controller.model.xml.Version20SensorBuilder.build(Version20SensorBuilder.java:287)
at org.openremote.controller.deployer.Version20ModelBuilder.buildSensorObjectModelFromXML(Version20ModelBuilder.java:858)
at org.openremote.controller.deployer.Version20ModelBuilder.buildSensorModel(Version20ModelBuilder.java:701)
at org.openremote.controller.deployer.Version20ModelBuilder.build(Version20ModelBuilder.java:595)
at org.openremote.controller.deployer.AbstractModelBuilder.buildModel(AbstractModelBuilder.java:154)
at org.openremote.controller.service.Deployer.startup(Deployer.java:1057)
at org.openremote.controller.service.Deployer.startController(Deployer.java:352)
at org.openremote.controller.spring.SpringContext.initializeController(SpringContext.java:111)
at org.openremote.controller.service.ServiceContext.init(ServiceContext.java:544)
at org.openremote.controller.bootstrap.Startup.loadServiceContext(Startup.java:89)
at org.openremote.controller.bootstrap.servlet.ServletStartup.initializeServiceContext(ServletStartup.java:195)
at org.openremote.controller.bootstrap.servlet.ServletStartup.contextInitialized(ServletStartup.java:109)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4342)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:926)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:889)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1149)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)


In /volume1/@appstore/OpenRemote/webapps/controller/zwave - there is nothing.

With the controller 2.1.1, it worked well. As it is now to get a working RXTX?

пятница, 2 сентября 2016 г., 9:56:22 UTC+3 пользователь Rainer Hitz написал:

Rainer Hitz

unread,
Sep 4, 2016, 12:19:13 AM9/4/16
to OpenRemote
We've replaced RXTX with the nrjavaserial library. The system specific libraries in the native directory are not needed anymore.

What hardware/OS are you using ?

Tehnoinstyle Aleksey

unread,
Sep 4, 2016, 4:19:26 AM9/4/16
to OpenRemote

The app OpenRemote installed on Synology NAS with DSM6.0.1. I use the AeonLab z-wave stick S2. Driver for USB stick installed.

Введите код.../$ uname -a
Linux DS3615ms 3.10.35 #1 SMP Tue Feb 2 17:44:24 CET 2016 x86_64 GNU/Linux synology_bromolow_3615xs

Введите код...[   39.497367] usbcore: registered new interface driver usbserial
[   39.602538] usbcore: registered new interface driver ftdi_sio
[   39.602744] usbserial: USB Serial support registered for FTDI USB Serial Devi                                                                                        ce
[   39.687906] usbcore: registered new interface driver cp210x
[   39.688033] usbserial: USB Serial support registered for cp210x
[   39.696010] usbcore: registered new interface driver pl2303
[   39.696202] usbserial: USB Serial support registered for pl2303
[   39.715675] usbcore: registered new interface driver ch341
[   39.715812] usbserial: USB Serial support registered for ch341-uart
[   39.736487] usbcore: registered new interface driver ti_usb_3410_5052
[   39.736616] usbserial: USB Serial support registered for TI USB 3410 1 port a                                                                                        dapter
[   39.736778] usbserial: USB Serial support registered for TI USB 5052 2 port a                                                                                        dapter
[  164.753353] usb 4-1: new full-speed USB device number 2 using uhci_hcd
[  164.932899] cp210x 4-1:1.0: cp210x converter detected
[  165.056277] usb 4-1: reset full-speed USB device number 2 using uhci_hcd
[  165.212868] usb 4-1: cp210x converter now attached to ttyUSB0
root@DS3615ms:~#



Earlier app OpenRemote 2.1.1 with Z-Wave version 2.0.1 was installed on DSM5.1 and everything worked well.

воскресенье, 4 сентября 2016 г., 7:19:13 UTC+3 пользователь Rainer Hitz написал:

Tehnoinstyle Aleksey

unread,
Sep 4, 2016, 8:09:54 AM9/4/16
to OpenRemote
I tried to run the application Domoticz, Z-Wave stick and other Z-Wave devices are normally defined and work.

2016-09-04 14:57:49.609 OpenZWave: Starting...
2016-09-04 14:57:49.610 OpenZWave: Version: 1.4-2133-gb754444-dirty
2016-09-04 14:57:49.610 OpenZWave: using config in: /usr/local/domoticz/Config/
2016-09-04 14:57:49.761 OpenZWave: Driver Ready
2016-09-04 14:57:49.761 OpenZWave: New Node added. HomeID: 25483747, NodeID: 1 (0x01)
2016-09-04 14:57:49.762 OpenZWave: New Node added. HomeID: 25483747, NodeID: 1 (0x01)
2016-09-04 14:57:49.762 OpenZWave: New Node added. HomeID: 25483747, NodeID: 2 (0x02)
2016-09-04 14:57:49.762 OpenZWave: New Node added. HomeID: 25483747, NodeID: 2 (0x02)
2016-09-04 14:57:49.762 OpenZWave: New Node added. HomeID: 25483747, NodeID: 3 (0x03)
2016-09-04 14:57:49.763 OpenZWave: New Node added. HomeID: 25483747, NodeID: 3 (0x03)
2016-09-04 14:57:49.763 OpenZWave: New Node added. HomeID: 25483747, NodeID: 4 (0x04)
2016-09-04 14:57:49.763 OpenZWave: New Node added. HomeID: 25483747, NodeID: 4 (0x04)
2016-09-04 14:57:49.763 OpenZWave: New Node added. HomeID: 25483747, NodeID: 5 (0x05)
2016-09-04 14:57:49.764 OpenZWave: New Node added. HomeID: 25483747, NodeID: 5 (0x05)
2016-09-04 14:57:49.764 OpenZWave: New Node added. HomeID: 25483747, NodeID: 7 (0x07)
2016-09-04 14:57:49.765 OpenZWave: New Node added. HomeID: 25483747, NodeID: 7 (0x07)



воскресенье, 4 сентября 2016 г., 7:19:13 UTC+3 пользователь Rainer Hitz написал:

Tehnoinstyle Aleksey

unread,
Sep 6, 2016, 10:03:47 AM9/6/16
to OpenRemote
Hi Rainer.
There is a solution to how to get the job Z-wave stick and the new controller OpenRemote?

Now not only works Z-wave protocol after upgrade from 2.1.1 to 2.6.2. Help me please with him.

воскресенье, 4 сентября 2016 г., 7:19:13 UTC+3 пользователь Rainer Hitz написал:

Michał J

unread,
Sep 7, 2016, 5:17:00 AM9/7/16
to OpenRemote
Hi Rainer,

Regarding new commands, should I just put command from the list in the edit box of the command definition?
Any guide to be released?


Best regards,
Michal

Rainer Hitz

unread,
Sep 8, 2016, 9:19:42 AM9/8/16
to OpenRemote
You can use all listed commands in the "Command" text box like in the following example:


Admittedly the Z-Wave command documentation is currently not perfect to say the least. We intend to change that in the future but I cannot promise any date.

Tehnoinstyle Aleksey

unread,
Sep 8, 2016, 9:29:03 AM9/8/16
to OpenRemote
Hi, Rainer.
How can I get working with Z-wave on controller 2.6.2?
Help me please.

четверг, 8 сентября 2016 г., 16:19:42 UTC+3 пользователь Rainer Hitz написал:

Rainer Hitz

unread,
Sep 8, 2016, 10:12:06 AM9/8/16
to OpenRemote
You could start the OpenRemote controller as root in order to check if it's an access rights problem on you Synology NAS.

Tehnoinstyle Aleksey

unread,
Sep 8, 2016, 11:08:03 AM9/8/16
to OpenRemote
How to do it? I have little knowledge of Linux.

I have to run in a terminal from the "root":

> chown -R root.users /volume1/@appstore/OpenRemote/webapps

instead:

> chown -R openremote.users /volume1/@appstore/OpenRemote/webapps

yes? or no.

четверг, 8 сентября 2016 г., 17:12:06 UTC+3 пользователь Rainer Hitz написал:

Stuart Hanlon

unread,
Sep 8, 2016, 12:52:15 PM9/8/16
to OpenRemote
Or you can prefix a command with 'sudo', which will run it with root privileges.

(You'll be asked for your user password)

Tehnoinstyle Aleksey

unread,
Sep 8, 2016, 2:51:45 PM9/8/16
to OpenRemote
Only after:

root@DS3615ms:~# sudo chown -R root.users /volume1/@appstore/OpenRemote/webapps
root@DS3615ms:~# sudo chown -R root.users /volume1/@appstore/OpenRemote
root@DS3615ms:~# ls -lh /dev/ttyUSB0
crwxrwxrwx 1 root dialout 188, 0 Sep  6 09:43 /dev/ttyUSB0
root@DS3615ms:~# sudo chown -R root.uucp /var/lock
root@DS3615ms:~# sudo chown -R root.dialout /dev/ttyUSB0


I got a job Z-wave.

--------------------------------------------------------------------

  OpenRemote Z-Wave protocol version : '3.0.0'

--------------------------------------------------------------------

DEBUG 2016-09-08 21:30:25,512 (Z-Wave): Connection_Manager          : Adding shutdown hook to manage unclosed Z-Wave connections in case of controller exit.
INFO 2016-09-08 21:30:25,621 (Z-Wave):  Serial_Port                 : Opening the serial port [COM port: /dev/ttyUSB0, Communication Layer: RXTX]...
INFO 2016-09-08 21:30:25,788 (Z-Wave):  Serial_Port                 : The serial port [COM port: /dev/ttyUSB0, Communication Layer: RXTX] has been successfully opened.
DEBUG 2016-09-08 21:30:25,876 (Z-Wave): Controller                  : Retrieving Z-Wave controller firmware version and library type...
DEBUG 2016-09-08 21:30:25,892 (Z-Wave): Controller_API              : Enqueue (queue count=0) Z-Wave function call 'ZW_Version'.
DEBUG 2016-09-08 21:30:25,892 (Z-Wave): Controller_API              : Dequeue (queue count=0) Z-Wave function call 'ZW_Version'.
DEBUG 2016-09-08 21:30:25,896 (Z-Wave): TX_Session_Layer            : Executing Z-Wave function call 'ZW_Version'...
DEBUG 2016-09-08 21:30:25,914 (Z-Wave): TX_Frame_Layer              : Send data frame [0x01, 0x03, 0x00, 0x15, 0xE9].
DEBUG 2016-09-08 21:30:25,933 (Z-Wave): RX_Serial_Port_RXTX         : Data bytes read : [0x06]
DEBUG 2016-09-08 21:30:25,935 (Z-Wave): RX_Frame_Layer              : ACK -> Data frame [0x01, 0x03, 0x00, 0x15, 0xE9] transmission OK.
DEBUG 2016-09-08 21:30:25,936 (Z-Wave): RX_Session_Layer            : ACK -> Z-Wave function 'ZW_Version' has been successfully sent - waiting 5,000 [ms] for response frame.
DEBUG 2016-09-08 21:30:25,938 (Z-Wave): RX_Serial_Port_RXTX         : Data bytes read : [0x01, 0x10, 0x01, 0x15, 0x5A, 0x2D, 0x57, 0x61, 0x76, 0x65, 0x20, 0x32, 0x2E, 0x37, 0x38, 0x00, 0x01, 0x9B]
DEBUG 2016-09-08 21:30:25,946 (Z-Wave): RX_Frame_Layer              : Data frame [0x01, 0x10, 0x01, 0x15, 0x5A, 0x2D, 0x57, 0x61, 0x76, 0x65, 0x20, 0x32, 0x2E, 0x37, 0x38, 0x00, 0x01, 0x9B] has been received.
DEBUG 2016-09-08 21:30:25,950 (Z-Wave): RX_Session_Layer            : Response received [0x01, 0x10, 0x01, 0x15, 0x5A, 0x2D, 0x57, 0x61, 0x76, 0x65, 0x20, 0x32, 0x2E, 0x37, 0x38, 0x00, 0x01, 0x9B] -> Z-Wave function 'ZW_Version' successfully executed.
INFO 2016-09-08 21:30:25,956 (Z-Wave):  Z-Wave firmware version     : Z-Wave 2.78
INFO 2016-09-08 21:30:25,956 (Z-Wave):  Z-Wave library type         : ZW_LIB_CONTROLLER_STATIC
DEBUG 2016-09-08 21:30:25,957 (Z-Wave): Controller                  : Retrieving serial API capabilities...
DEBUG 2016-09-08 21:30:25,961 (Z-Wave): Controller_API              : Enqueue (queue count=1) Z-Wave function call 'SERIAL_API_GetCapabilities'.
DEBUG 2016-09-08 21:30:25,961 (Z-Wave): Controller_API              : Dequeue (queue count=0) Z-Wave function call 'SERIAL_API_GetCapabilities'.
DEBUG 2016-09-08 21:30:25,962 (Z-Wave): TX_Session_Layer            : Executing Z-Wave function call 'SERIAL_API_GetCapabilities'...



I do not restart the server after you follow these commands.
But in boot.log not record anything.
Tomorrow I will try the job Z-wave after the server is rebooted.

четверг, 8 сентября 2016 г., 19:52:15 UTC+3 пользователь Stuart Hanlon написал:

Tehnoinstyle Aleksey

unread,
Sep 9, 2016, 5:54:03 AM9/9/16
to OpenRemote
Hi, Rainer.

For USB-RXTX on Synology with DSM6.0.1.

Z-Wave stick works only when the rights to the directory /var/run/lock - 777. But after you restart the server, the rights to the directory again become 755.

Problem was solved in the following way. I returned the access rights as it was before.

sudo chown -R openremote.users /volume1/@appstore/OpenRemote
sudo chown -R openremote.users /volume1/@appstore/OpenRemote/webapps

In the file /var/packages/UsbSerialDrivers/scripts/start-stop-status I added following strings:

sudo chown -R root.uucp /var/lock
sudo chmod 777 /var/run/lock
sudo chown -R root.dialout /dev/ttyUSB0
sudo chmod 777 /dev/ttyUSB0

#!/bin/sh

# Package
PACKAGE="UsbSerialDrivers"
DNAME="lsusb"

# Others
INSTALL_DIR="/usr/local/${PACKAGE}"
RUNAS="root"
USBUTILS="${INSTALL_DIR}/bin/lsusb"
    

case $1 in
    start)

    insmod /lib/modules/usbserial.ko > /dev/null
    insmod /lib/modules/ftdi_sio.ko >/dev/null
    insmod ${INSTALL_DIR}/modules/usbserial.ko >/dev/null
    insmod ${INSTALL_DIR}/modules/ftdi_sio.ko >/dev/null
    insmod ${INSTALL_DIR}/modules/cp210x.ko >/dev/null
    insmod ${INSTALL_DIR}/modules/pl2303.ko >/dev/null
    insmod ${INSTALL_DIR}/modules/ch341.ko >/dev/null
    insmod ${INSTALL_DIR}/modules/ti_usb_3410_5052.ko >/dev/null
    sudo chown -R root.uucp /var/lock
    sudo chmod 777 /var/run/lock
    sudo chown -R root.dialout /dev/ttyUSB0
    sudo chmod 777 /dev/ttyUSB0

    sleep 2
    echo $(date +"%D-%T") chmod 777 completed successfuly >> /volume1/@appstore/UsbSerialDrivers/logs/UsbSerialDrivers.log

        exit 0
        ;;
    stop)
    
        exit 0
        ;;
    status)
        exit 0
        ;;
    log)
        exit 1
        ;;
    *)
        exit 1
        ;;
esac

Now Z-Wave stick normally it works, and works after the server reboots. But I do not know - it the correct solution? Thankyou.


четверг, 8 сентября 2016 г., 17:12:06 UTC+3 пользователь Rainer Hitz написал:
Reply all
Reply to author
Forward
0 new messages