Unknown ZWave device, Aeotec Nano Dimmer ZW511

New to this openHab but enjoying it so far. Now for the story:

  • I managed to get openhabian (v1.2) installed!
  • Got WIFI set up as AP to talk to lifx bulb – success
  • Added lifx bulb to openhabian – success
  • Added aeotec zwave dongle to openhabian – success
  • Added aeotec 4in1 multisensor to openhabian – eventual success
  • Added aeotec 6in1 multisensor to openhabian – success
  • Failure to add aeotec nano dimmer (ZW111-B) – Its reported as an unknown device – I think is the same as this one http://products.z-wavealliance.org/products/2095 but the -B for AUS

From other posts I see there is a device database, I couldn’t find ZW111 in there and I’m not sure what is needed to create an entry but I’m up for trying. Below is the rest API output for the thing and a stack trace. Any ideas on where to head from here?

FWIW I tried updating openhab to the nightly but jetty started so I uninstalled and went back to 2.0

Infos:
I have this: http://openhabianpi:8080/rest/things/zwave:device:88bf0286:node7

  "statusInfo": {
    "status": "ONLINE",
    "statusDetail": "NONE"
  },
  "label": "Z-Wave Node 7 (0086:0203:006F:1.2)",
  "bridgeUID": "zwave:serial_zstick:88bf0286",
  "configuration": {
    "group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@1fee2d2": [],
    "switchall_mode": "SWITCH_ALL_INCLUDE_ON_OFF",
    "group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@15ea344": [],
    "group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@1db99da": [],
    "group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@1e603d3": []
  },
  "properties": {
    "zwave_class_basic": "ROUTING_SLAVE",
    "zwave_class_generic": "MULTILEVEL_SWITCH",
    "zwave_frequent": "false",
    "zwave_neighbours": "1",
    "zwave_version": "1.2",
    "zwave_listening": "true",
    "zwave_plus_devicetype": "LIGHT_DIMMER_SWITCH",
    "zwave_deviceid": "111",
    "zwave_nodeid": "7",
    "zwave_routing": "true",
    "zwave_beaming": "true",
    "zwave_class_specific": "POWER_SWITCH_MULTILEVEL",
    "zwave_manufacturer": "134",
    "zwave_devicetype": "515"
  },
  "UID": "zwave:device:88bf0286:node7",
  "thingTypeUID": "zwave:device",
  "channels": []
}```

**Stack trace during startup:**
```    2017-04-14 14:26:05.683 [INFO ] [.dashboard.internal.DashboardService] - Started dashboard at /start
    2017-04-14 14:26:08.921 [INFO ] [basic.internal.servlet.WebAppServlet] - Started Basic UI at /basicui/app
    2017-04-14 14:26:09.050 [INFO ] [arthome.ui.paper.internal.PaperUIApp] - Started Paper UI at /paperui
    2017-04-14 14:26:10.490 [INFO ] [panel.internal.HABPanelDashboardTile] - Started HABPanel at /habpanel
    2017-04-14 14:26:10.685 [INFO ] [ui.habmin.internal.servlet.HABminApp] - Started HABmin servlet at /habmin
    2017-04-14 14:26:14.008 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Connecting to serial port '/dev/ttyACM0'
    2017-04-14 14:26:14.096 [INFO ] [ing.zwave.handler.ZWaveSerialHandler] - Serial port is initialized
    2017-04-14 14:26:14.114 [INFO ] [mmandclass.ZWaveSecurityCommandClass] - Update networkKey
    2017-04-14 14:26:14.140 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - Controller handler not found. Cannot handle command without ZWave controller.
    2017-04-14 14:26:14.146 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - Controller handler not found. Cannot handle command without ZWave controller.
    2017-04-14 14:26:14.147 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - Controller handler not found. Cannot handle command without ZWave controller.
    2017-04-14 14:26:14.148 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - Controller handler not found. Cannot handle command without ZWave controller.
    2017-04-14 14:26:14.150 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - Controller handler not found. Cannot handle command without ZWave controller.
    2017-04-14 14:26:14.151 [INFO ] [ve.internal.protocol.ZWaveController] - Starting ZWave controller
    2017-04-14 14:26:14.151 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - Controller handler not found. Cannot handle command without ZWave controller.
    2017-04-14 14:26:14.152 [INFO ] [ve.internal.protocol.ZWaveController] - ZWave timeout is set to 5000ms. Soft reset is false.
    2017-04-14 14:26:17.445 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 1: Node found
    2017-04-14 14:26:17.447 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 5: Node found
    2017-04-14 14:26:17.450 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 6: Node found
    2017-04-14 14:26:17.452 [INFO ] [age.SerialApiGetInitDataMessageClass] - NODE 7: Node found
    2017-04-14 14:26:17.454 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller using Controller API
    2017-04-14 14:26:17.456 [INFO ] [age.SerialApiGetInitDataMessageClass] - ZWave Controller is Primary Controller
    2017-04-14 14:26:17.458 [INFO ] [age.SerialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
    2017-04-14 14:26:17.460 [INFO ] [age.SerialApiGetInitDataMessageClass] - # Nodes = 4
    2017-04-14 14:26:17.462 [INFO ] [age.SerialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
    2017-04-14 14:26:18.990 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 7: Device discovery could not resolve to a thingType! 0086:0203:006F::1.2
    2017-04-14 14:26:18.998 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:88bf0286:node7' to inbox.
    2017-04-14 14:26:19.001 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 6: Device discovery could not resolve to a thingType! 0086:0203:006F::1.2
    2017-04-14 14:26:19.024 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:88bf0286:node6' to inbox.
    2017-04-14 14:26:19.067 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Size error 4<>1 from config_255_4_wo
    2017-04-14 14:26:19.102 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...
    2017-04-14 14:26:23.428 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 7: Timeout while sending message. Requeueing - 0 attempts left!
    2017-04-14 14:26:23.429 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 7: Got an error while sending data. Resending message.
    2017-04-14 14:26:30.257 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Got an error while sending data. Resending message.
    2017-04-14 14:26:34.373 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Got an error while sending data. Resending message.
    2017-04-14 14:26:38.460 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:26:42.606 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:26:46.771 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:26:50.857 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:26:55.002 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:27:05.227 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:27:45.196 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:29:05.226 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:29:57.329 [WARN ] [l.serialmessage.SendDataMessageClass] - NODE 5: Already processed another send data request for this callback Id, ignoring.
    2017-04-14 14:30:02.299 [ERROR] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Timeout while sending message. Requeueing - 0 attempts left!
    2017-04-14 14:30:43.480 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:30:43.681 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:31:27.840 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:31:28.039 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:31:41.082 [ERROR] [alization.ZWaveNodeInitStageAdvancer] - NODE 6: Node advancer: Retries exceeded at PING
    2017-04-14 14:33:44.516 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Initialising Thing Node...
    2017-04-14 14:33:57.311 [WARN ] [l.serialmessage.SendDataMessageClass] - NODE 5: Already processed another send data request for this callback Id, ignoring.
    2017-04-14 14:34:02.284 [WARN ] [ocol.ZWaveController$ZWaveSendThread] - NODE 5: Too many retries. Discarding message: Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=5, callback=31, payload=05 01 00
    2017-04-14 14:35:52.731 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:35:52.932 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:37:05.214 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:37:57.401 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:37:57.474 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:37:59.945 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '45' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_SensorRelativeHumidity' to handler for channel 'zwave:device:9bee998c:node2:sensor_relhumidity', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:38:02.154 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '23.5' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_SensorTemperature' to handler for channel 'zwave:device:9bee998c:node2:sensor_temperature', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:38:03.098 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '1000' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_SensorLuminance' to handler for channel 'zwave:device:9bee998c:node2:sensor_luminance', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:38:03.832 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '92' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BatteryLevel' to handler for channel 'zwave:device:9bee998c:node2:battery-level', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:38:04.471 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Size error 4<>1 from config_255_4_wo
    2017-04-14 14:38:04.474 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...
    2017-04-14 14:38:04.517 [ERROR] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Size error 4<>1 from config_255_4_wo
    2017-04-14 14:38:04.519 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 5: Initialising Thing Node...
    2017-04-14 14:42:03.452 [WARN ] [age.RequestNetworkUpdateMessageClass] - RequestNetworkUpdate not placed on stack.
    2017-04-14 14:42:06.731 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:42:06.930 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:47:45.202 [ERROR] [l.serialmessage.SendDataMessageClass] - NODE 6: Node is DEAD. Dropping message.
    2017-04-14 14:49:12.260 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
    java.lang.IllegalArgumentException: Illegal parameter size 5
            at org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter.<init>(ZWaveConfigurationParameter.java:39)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveConfigurationCommandClass.processConfigurationReport(ZWaveConfigurationCommandClass.java:129)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveConfigurationCommandClass.handleApplicationCommandRequest(ZWaveConfigurationCommandClass.java:86)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:248)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:214)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[192:org.openhab.binding.zwave:2.0.0]
    2017-04-14 14:53:22.488 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:53:22.692 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:53:57.962 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '92' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BatteryLevel' to handler for channel 'zwave:device:9bee998c:node2:battery-level', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:53:58.162 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '1000' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_SensorLuminance' to handler for channel 'zwave:device:9bee998c:node2:sensor_luminance', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:53:59.420 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '23.4' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_SensorTemperature' to handler for channel 'zwave:device:9bee998c:node2:sensor_temperature', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:53:59.665 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update '45' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_SensorRelativeHumidity' to handler for channel 'zwave:device:9bee998c:node2:sensor_relhumidity', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:57:43.039 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:57:43.260 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 14:59:34.265 [ERROR] [ve.internal.protocol.ZWaveController] - Exception during ZWave thread: Input 2. {}
    java.lang.IllegalArgumentException: Illegal parameter size 5
            at org.openhab.binding.zwave.internal.protocol.ZWaveConfigurationParameter.<init>(ZWaveConfigurationParameter.java:39)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveConfigurationCommandClass.processConfigurationReport(ZWaveConfigurationCommandClass.java:129)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.commandclass.ZWaveConfigurationCommandClass.handleApplicationCommandRequest(ZWaveConfigurationCommandClass.java:86)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.serialmessage.ApplicationCommandMessageClass.handleRequest(ApplicationCommandMessageClass.java:119)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingRequestMessage(ZWaveController.java:248)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController.handleIncomingMessage(ZWaveController.java:214)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController.access$7(ZWaveController.java:208)[192:org.openhab.binding.zwave:2.0.0]
            at org.openhab.binding.zwave.internal.protocol.ZWaveController$ZWaveInputThread.run(ZWaveController.java:1324)[192:org.openhab.binding.zwave:2.0.0]
    2017-04-14 15:06:32.740 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'OFF' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 15:06:32.943 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_Alarm' to handler for channel 'zwave:device:9bee998c:node2:alarm_general', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.
    2017-04-14 15:08:17.321 [WARN ] [ome.core.thing.internal.ThingManager] - Cannot delegate update 'ON' for item 'ZWaveNode2ZW0744InOneMultiSensorG5_BinarySensor' to handler for channel 'zwave:device:9bee998c:node2:sensor_binary', because no thing with the UID 'zwave:device:9bee998c:node2' could be found.```

Hi,
Take a look at this link http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-database-guide. This should fill you in on how to create the entry.

Once you have an account, send me a mail so I can update your access for editing. Any problems or questions and I’ll try and help.

Cheers
Chris

Hi Chris, thanks for the link. I’ve created an account ‘Frog’. I’ll have a crack at adding a device.

Thanks

Thanks - I’ve updated your access - if you have any problems/questions, just yell…

Cheers
Chris

Cheers job for tomorrow. :slight_smile:

Okay chris, i’ve got the XML imported and I’ve started adding detail. I’m looking at ‘Configuration Parameters’ and am not sure what to do with parameter 102 from http://products.z-wavealliance.org/products/2095/configs. It has 4 options which look like they should be a multi select but i’m not sure if

  1. They actually are a multi selection (ie the device can be configured to send V and A but not W and kWh) or the device can only send one report.
  2. How to define in the database if they are a multi selection option

Cheers.

Also I’ve found this from openzwave https://github.com/OpenZWave/open-zwave/blob/8e721d25bf44b9d2bb760badc55c645bbbd7685f/config/aeotec/zw111.xml

Which contains

            <Help>
                Defines the type of report sent for reporting group 2.
                1 is meter report for voltage.
                2 is meter report for current.
                4 is meter report for watts.
                8 is meter report for kilowatts.
                Value 1 (msb) Reserved
                Value 2 Reserved
                Value 3 Reserved
                Value 4 (lsb) bits 7-4 reserved
                bit 3 current
                bit 2 voltage
                bit 1 watt
                bit 0 kWh
            </Help>
        </Value>```

Making me think it is in fact a multi select where each option applies to a bit.

Just a thought, is it possible to import the zwave alliance xml into the database? ie this one http://products.z-wavealliance.org/Products/2095/XML

Yes - there’s no way to make this a multiselect as such - there’s two options. Either just add a value and in the description put how to add the bits together to make the value (which is what’s done on most other Aeon devices since this parameter is common to all Aeon devices), or, we could add separate parameters for each bit…

The database allows you to create a ‘sub-parameter’ where you can put a bitmask to single out a range of bits (or a single bit). So, you could do this, but to be honest, I’d suggest to just add the single parameter with the description.

Interesting… This is the first time I’ve seen one of their XML files that actually has configuration in it - mostly they just have device information.

It’s not possible right now, but I will take a look at this as if the Alliance is going to start doing this then it makes sense to add the import.

Hi Chris, Thanks for the advice, will do.
I’ve accidentally updated the incorrect device (I had two browser windows open and looks like I either updated the wrong one or the request to the server referenced the wrong ID) Either way. The update that I made to param 102 for http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/355#parameters should be rejected! And param 103. Lesson learnt don’t have two browser windows open on two different devices in the database.

Also I couldn’t find way to remove options from param 102 for http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/576 if you could remove them as well.

Cheers

Hopefully all done :slight_smile:

:slight_smile: Ta!
I’m not sure what to enter for the Command Class - Hail? I don’t see any details on the z-wavealliance.org :confused:

I believe all the data i have access to has been entered so please take a look.
I wasn’t sure what to do with the controller flag in the association so I left it as is (un checked)

Cheers!

There’s nothing that can be set for HAIL - the binding will use it if it’s announced, but otherwise don’t worry too much about it.

If the group is used to send reports to a controller (eg a lifeline group) then it should be checked. This tells the binding that it should automatically configure an association to itself for this group so it receives notifications.

Thanks.
Chris

Ahh okay, I see you’ve already updated the controller flag. Ta.

So now how to test? I’d like to see the dimmer actually working :slight_smile: :slight_smile: :slight_smile:

You need to update to the latest snapshot which should have this device included now.

So I eventually got a a newer version of the binding installed, the dimmer was recognised and seems to function normally. I had to build a version of the binding that included a newer xml from the database because I noticed that a lot of the parameters are not shown :slight_smile:

Thanks for the assist!

Hi I have downloaded the 2.1.0 snapshot on 28th may 2017 and installed the zwave 2.1.0 binding but still the device is unrecognised. I deinstalled the 2.0.0 zwave binding first.

Any ideas?

Please provide the type/id information for your device - you might have one that is different to what’s in the database as there are normally many different versions (eg regionally).

Thanks for the reply

Here is the information I think you need…
Z-Wave Node 3 (0086:0003:006F:1.2)

Manutacturer 0086 AEON Labs
Type / ID 0003:006f
Firmware Version1.2
Z-Wave Plus Node TypeLIGHT_DIMMER_SWITCH
Basic ClassROUTING_SLAVE
Generic ClassMULTILEVEL_SWITCH
Specific ClassPOWER_SWITCH_MULTILEVEL
Using Security
Routing
Listening
Frequently Listening
Beaming
Neighbours 2 nodes 1, 2

These IDs are already in the database, so it should be detected ok - so long as you’re certain you’re running a recent version.

If so, then I’d suggest to look at the debug log to see if it shows what’s happening.