Starting out... OH2, Z-wave lights/dimmers working, nothing else Z-wave is (multisensor, etc)

[NOTORIOUS_VR]

New to OH, previously running Domoticz.

Configured my Aeon Z-wave stick, OH2 started to find the existing devices almost immediately.

Was able to get the lights working without much of a hassle, but no matter what the Multisensor 6 won’t show any values.

Before going further I would like to find out why I cannot get this to work.

That said, I also noticed PaperUI setup seems to be kind of “half-a$$d” where to use other functions of OH correctly you still need a proper sitemap, items, etc.

So I used the homebuilder to start with basics, and then started to bind the z-wave devices in the default.items file that I created from the homebuilder. This created duplicate bindings from the PaperUI which I then removed to clean it all up. Currently the only bindings are from the files.

That said, I cannot seem to get any other z-wave devices to work - mainly sensors. I have 1 multisensor, 1 motion/temp sensor, 2 door contact sensor (one w/ light+temp included). None seem to be able to return any values/states.

• Platform information:
  • Hardware: ESXi - 1 CPU, 2 GB RAM, 20 GB HDD
  • OS: Ubuntu 16.04 (mini/netboot)
  • Java Runtime Environment: Zulu Embedded OpenJDK Java 8
  • openHAB version: Current stable OH2 (setup via OpenHabian)
• Issue of the topic: please be detailed explaining your issue
• Please post configurations (if applicable):
  • Items configuration related to the issue

Group     Home                       "BATCAVE"                <house>

Group     LivingDining               "Living & Dining Room"   <sofa>          (Home)
Group     Balcony                    "Balcony"                                (Home)
Group     Bedroom                    "Bedroom"                <bedroom>       (Home)
Group     Bathroom                   "Bathroom"               <bath>          (Home)
Group     Wardrobe                   "Wardrobe"               <wardrobe>      (Home)
Group     Entryway                   "Entryway"               <frontdoor>     (Home)
Group     Kitchen                    "Kitchen"                <kitchen>       (Home)

Dimmer    LR_AV_LEDs                 "AV Unit LEDs"                                 <light>         (LivingDining, gLight)            {channel="zwave:device:f019eab0:node9:switch_dimmer"}
Dimmer    LR_Couch_Lamp              "LR Couch Lamp"                                   <light>         (LivingDining, gLight)            {channel="zwave:device:f019eab0:node4:switch_dimmer"}
Dimmer    LR_Floor_Lamp              "AV Floor Lamp"                                <light>         (LivingDining, gLight)            {channel="zwave:device:f019eab0:node8:switch_dimmer"}
Contact   LivingDining_Motion        "Motion Sensor: [MAP(motion.map):%s]"          <motion>        (LivingDining, gMotion)           {channel="zwave:device:f019eab0:node11:sensor_binary"}
Number    LivingDiningMulti_Temperature   "Temperature: [%.1f °C]"                       <temperature>   (LivingDining, gTemperature)      {channel="zwave:device:f019eab0:node11:sensor_temperature"}
Number    LivingDiningMulti_Humidity      "Humidity: [%.0f %%]"                          <humidity>      (LivingDining, gHumidity)         {channel="zwave:device:f019eab0:node11:sensor_relhumidity"}
Number    LivingDiningMulti_LUX           "Luminance: [%.0f Lux]"                        <lux>           (LivingDining, gLUX)              {channel="zwave:device:f019eab0:node11:sensor_luminance"}
Number    LivingDiningMulti_Battery       "Battery: [%d %%]"                             <lux>           (LivingDining, gLUX)              {channel="zwave:device:f019eab0:node11:battery-level"}
Switch    Balcony_Light              "Light"                  <light>         (Balcony, gLight)                 {channel=""}
Switch    Bedroom_Light              "Light"                  <light>         (Bedroom, gLight)                 {channel=""}
Contact   Bedroom_Door               "Door"                   <door>          (Bedroom, gDoor)                  {channel=""}
Number    Bedroom_Temperature        "Temperature"            <temperature>   (Bedroom, gTemperature)           {channel=""}
Switch    Bathroom_Light             "Light"                  <light>         (Bathroom, gLight)                {channel=""}
Switch    Wardrobe_Light             "Light"                  <light>         (Wardrobe, gLight)                {channel=""}
Switch    Entryway_Light             "Light"                  <light>         (Entryway, gLight)                {channel=""}
Contact   Entryway_Door              "Door [%s]"                   <door>          (Entryway, gDoor)                 {channel=""}
Switch    Kitchen_Light              "Light"                  <light>         (Kitchen, gLight)                 {channel=""}
Contact   Kitchen_Motion             "Motion Sensor: [MAP(motion.map):%s]"               <motion>        (Kitchen, gMotion)                {channel="zwave:device:f019eab0:node17:sensor_binary"}
Number    Kitchen_Temperature        "Temperature: [%.1f °C]"                            <temperature>   (Kitchen, gTemperature)           {channel="zwave:device:f019eab0:node17:sensor_temperature"}

Group:Switch:OR(ON, OFF)         gLight         "Light"           <light>         (Home)
Group:Switch:OR(ON, OFF)         gMotion        "Motion Sensor"   <motion>        (Home)
Group:Number:AVG                 gTemperature   "Temperature"     <temperature>   (Home)
Group:Number:AVG                 gHumidity      "Humidity"        <humidity>      (Home)
Group:Number:AVG                 gLUX           "Luminance"       <lux>           (Home)
Group:Contact:OR(OPEN, CLOSED)   gDoor          "Door"            <door>          (Home)

• Sitemap configuration related to the issue

sitemap default label="BATCAVE" {
    Frame {
        Group item=LivingDining
        Group item=Balcony
        Group item=Bedroom
        Group item=Bathroom
        Group item=Wardrobe
        Group item=Entryway
        Group item=Kitchen
    }

    Frame {
        Text label="Light" icon="light" {
            Default item=LivingDining_Light label="Living & Dining Room"
            Default item=Balcony_Light label="Balcony"
            Default item=Bedroom_Light label="Bedroom"
            Default item=Bathroom_Light label="Bathroom"
            Default item=Wardrobe_Light label="Wardrobe"
            Default item=Entryway_Light label="Entryway"
            Default item=Kitchen_Light label="Kitchen"
        }

        Text label="Motion Sensor" icon="motion" {
            Default item=LivingDining_Motion label="Living & Dining Room"
            Default item=Kitchen_Motion label="Kitchen"
        }

        Text label="Temperature" icon="temperature" {
            Default item=LivingDining_Temperature label="Living & Dining Room"
            Default item=Bedroom_Temperature label="Bedroom"
        }

        Text label="Humidity" icon="humidity" {
            Default item=LivingDining_Humidity label="Living & Dining Room"
        }

        Text label="Door" icon="door" {
            Default item=Bedroom_Door label="Bedroom"
            Default item=Entryway_Door label="Entryway"
        }
    }
}

Screenshot of PaperUI:
https://imgur.com/tPyiEGL

[sihui]

This created duplicate bindings from the PaperUI

Read chapter “Item linking” of the beginners doc:
https://docs.openhab.org/tutorials/beginner/configuration.html

If you want to use text files you should set that to OFF, otherwise you will be confused about the auto created items.

I cannot seem to get any other z-wave devices to work

First step is always: what does your openhab.log tell you?

[NOTORIOUS_VR]

First step is always: what does your openhab.log tell you?

You know that is a good question… While I did look at the log file quickly I didn’t see anything noteworthy.

But I will double check and see what it reports and post here again.

Thanks,

[NOTORIOUS_VR]

First step is always: what does your openhab.log tell you?

Here is a snippet (max of 32000 char allowable) of the ZWAVE log in DEBUG mode. If anyone can comment and let me know what I’m looking for.

Under Domoticz, every sensor is working just as it should FWIW.

09-Apr-2018 21:56:36.127 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=17, callback=55, payload=11 02 30 02 
09-Apr-2018 21:56:36.127 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 11 03 20 01 00 
09-Apr-2018 21:56:36.127 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=55, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
09-Apr-2018 21:56:36.128 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
09-Apr-2018 21:56:36.128 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Putting message SendData in wakeup queue.
09-Apr-2018 21:56:36.128 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
09-Apr-2018 21:56:36.159 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 00 11 0B 71 05 07 00 00 FF 07 00 01 08 00 72 
09-Apr-2018 21:56:36.163 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:36.163 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 11 00 04 00 11 0B 71 05 07 00 00 FF 07 00 01 08 00 72 
09-Apr-2018 21:56:36.163 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 11 00 04 00 11 0B 71 05 07 00 00 FF 07 00 01 08 00 72 
09-Apr-2018 21:56:36.164 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 11 0B 71 05 07 00 00 FF 07 00 01 08 00 
09-Apr-2018 21:56:36.164 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:36.164 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 17: Starting initialisation from DONE
09-Apr-2018 21:56:36.164 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@67549400 already registered
09-Apr-2018 21:56:36.165 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Incoming command class ALARM
09-Apr-2018 21:56:36.165 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 17: Received ALARM command V4
09-Apr-2018 21:56:36.165 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 17: Process NOTIFICATION_REPORT V4
09-Apr-2018 21:56:36.165 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 17: NOTIFICATION report - 7 = 0, event=0, status=255
09-Apr-2018 21:56:36.166 [DEBUG] [ernal.protocol.commandclass.ZWaveAlarmCommandClass] - NODE 17: Alarm Type = BURGLAR (7)
09-Apr-2018 21:56:36.166 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
09-Apr-2018 21:56:36.166 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveAlarmValueEvent
09-Apr-2018 21:56:36.166 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
09-Apr-2018 21:56:36.167 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
09-Apr-2018 21:56:36.167 [DEBUG] [nding.zwave.internal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
09-Apr-2018 21:56:36.167 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Updating channel state zwave:device:f019eab0:node17:alarm_burglar to OFF [OnOffType]
09-Apr-2018 21:56:36.168 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Immediate, dest=17, callback=55, payload=11 02 30 02 
09-Apr-2018 21:56:36.168 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 11 0B 71 05 07 00 00 FF 07 00 01 08 00 
09-Apr-2018 21:56:36.168 [DEBUG] [ernal.protocol.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=ApplicationCommandHandler, callback id=55, expected=ApplicationCommandHandler, cancelled=false        transaction complete!
09-Apr-2018 21:56:36.169 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
09-Apr-2018 21:56:36.169 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Putting message SendData in wakeup queue.
09-Apr-2018 21:56:36.169 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
09-Apr-2018 21:56:47.762 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Polling...
09-Apr-2018 21:56:47.763 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Polling zwave:device:f019eab0:node17:sensor_binary
09-Apr-2018 21:56:47.763 [DEBUG] [wave.internal.converter.ZWaveBinarySensorConverter] - NODE 17: Generating poll message for SENSOR_BINARY, endpoint 0
09-Apr-2018 21:56:47.763 [DEBUG] [rotocol.commandclass.ZWaveBinarySensorCommandClass] - NODE 17: Creating new message for application command SENSOR_BINARY_GET
09-Apr-2018 21:56:47.763 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Polling zwave:device:f019eab0:node17:sensor_temperature
09-Apr-2018 21:56:47.763 [DEBUG] [.internal.converter.ZWaveMultiLevelSensorConverter] - NODE 17: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
09-Apr-2018 21:56:47.764 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 17: Creating new message for command SENSOR_MULTI_LEVEL_GET
09-Apr-2018 21:56:47.764 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Polling zwave:device:f019eab0:node17:alarm_burglar
09-Apr-2018 21:56:47.764 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 17: Polling zwave:device:f019eab0:node17:battery-level
09-Apr-2018 21:56:47.764 [DEBUG] [ing.zwave.internal.converter.ZWaveBatteryConverter] - NODE 17: Generating poll message for BATTERY endpoint 0
09-Apr-2018 21:56:47.764 [DEBUG] [nal.protocol.commandclass.ZWaveBatteryCommandClass] - NODE 17: Creating new message for application command BATTERY_GET
09-Apr-2018 21:56:47.764 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Message already on the wake-up queue. Removing original.
09-Apr-2018 21:56:47.764 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Putting message SendData in wakeup queue.
09-Apr-2018 21:56:47.765 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Message already on the wake-up queue. Removing original.
09-Apr-2018 21:56:47.765 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Putting message SendData in wakeup queue.
09-Apr-2018 21:56:47.765 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Message already on the wake-up queue. Removing original.
09-Apr-2018 21:56:47.765 [DEBUG] [rnal.protocol.commandclass.ZWaveWakeUpCommandClass] - NODE 17: Putting message SendData in wakeup queue.
09-Apr-2018 21:56:51.478 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 02 03 80 03 64 14 
09-Apr-2018 21:56:51.486 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:51.486 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 02 03 80 03 64 14 
09-Apr-2018 21:56:51.486 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 02 03 80 03 64 14 
09-Apr-2018 21:56:51.486 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 03 80 03 64 
09-Apr-2018 21:56:51.486 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:51.486 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:51.486 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:51.487 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class BATTERY
09-Apr-2018 21:56:51.487 [DEBUG] [nal.protocol.commandclass.ZWaveBatteryCommandClass] - NODE 2: Received Battery Request
09-Apr-2018 21:56:51.487 [DEBUG] [nal.protocol.commandclass.ZWaveBatteryCommandClass] - NODE 2: Battery report value = 100
09-Apr-2018 21:56:51.487 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
09-Apr-2018 21:56:51.487 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
09-Apr-2018 21:56:51.487 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
09-Apr-2018 21:56:51.487 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:battery-level to 100 [DecimalType]
09-Apr-2018 21:56:51.488 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255
09-Apr-2018 21:56:56.466 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0E 00 04 00 02 08 31 05 04 64 00 12 0E 58 EF 
09-Apr-2018 21:56:56.474 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:56.474 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0E 00 04 00 02 08 31 05 04 64 00 12 0E 58 EF 
09-Apr-2018 21:56:56.474 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 0E 00 04 00 02 08 31 05 04 64 00 12 0E 58 EF 
09-Apr-2018 21:56:56.474 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 08 31 05 04 64 00 12 0E 58 
09-Apr-2018 21:56:56.474 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:56.474 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:56.474 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:56.474 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class SENSOR_MULTILEVEL
09-Apr-2018 21:56:56.474 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V2
09-Apr-2018 21:56:56.474 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Multi Level REPORT received
09-Apr-2018 21:56:56.474 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Type = Power(4), Scale = 0
09-Apr-2018 21:56:56.474 [DEBUG] [col.commandclass.ZWaveMultiLevelSensorCommandClass] - NODE 2: Sensor Value = 1183.32
09-Apr-2018 21:56:56.474 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMultiLevelSensorValueEvent
09-Apr-2018 21:56:56.474 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
09-Apr-2018 21:56:56.474 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 1183.32
09-Apr-2018 21:56:56.475 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:sensor_power to 1183.32 [DecimalType]
09-Apr-2018 21:56:56.475 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255
09-Apr-2018 21:56:56.482 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 02 0E 32 02 21 74 00 12 0E 58 00 00 00 00 00 00 C2 
09-Apr-2018 21:56:56.490 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:56.490 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 14 00 04 00 02 0E 32 02 21 74 00 12 0E 58 00 00 00 00 00 00 C2 
09-Apr-2018 21:56:56.490 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 14 00 04 00 02 0E 32 02 21 74 00 12 0E 58 00 00 00 00 00 00 C2 
09-Apr-2018 21:56:56.490 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 0E 32 02 21 74 00 12 0E 58 00 00 00 00 00 00 
09-Apr-2018 21:56:56.490 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:56.490 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:56.490 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:56.490 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class METER
09-Apr-2018 21:56:56.490 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Received METER command V2
09-Apr-2018 21:56:56.490 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Meter: Type=Electric(1), Scale=W(2), Value=1183.32
09-Apr-2018 21:56:56.490 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.490 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.490 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 1183.32
09-Apr-2018 21:56:56.490 [DEBUG] [nding.zwave.internal.converter.ZWaveMeterConverter] - Not the right scale E_KWh <> E_W
09-Apr-2018 21:56:56.490 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:meter_watts to 1183.32 [DecimalType]
09-Apr-2018 21:56:56.490 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255
09-Apr-2018 21:56:56.581 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 14 00 04 00 02 0E 32 02 21 64 00 8E 27 C9 00 F0 00 8E 27 7B D4 
09-Apr-2018 21:56:56.589 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:56.589 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 14 00 04 00 02 0E 32 02 21 64 00 8E 27 C9 00 F0 00 8E 27 7B D4 
09-Apr-2018 21:56:56.589 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 14 00 04 00 02 0E 32 02 21 64 00 8E 27 C9 00 F0 00 8E 27 7B D4 
09-Apr-2018 21:56:56.589 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 0E 32 02 21 64 00 8E 27 C9 00 F0 00 8E 27 7B 
09-Apr-2018 21:56:56.590 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:56.590 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:56.590 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:56.590 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class METER
09-Apr-2018 21:56:56.590 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Received METER command V2
09-Apr-2018 21:56:56.590 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Meter: Type=Electric(1), Scale=kWh(0), Value=9316.297
09-Apr-2018 21:56:56.590 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.591 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.591 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = METER, value = 9316.297
09-Apr-2018 21:56:56.591 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:meter_kwh to 9316.297 [DecimalType]
09-Apr-2018 21:56:56.591 [DEBUG] [nding.zwave.internal.converter.ZWaveMeterConverter] - Not the right scale E_W <> E_KWh
09-Apr-2018 21:56:56.591 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255
09-Apr-2018 21:56:56.682 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 04 00 02 12 60 0D 01 00 32 02 21 74 00 03 2F 28 00 00 00 00 00 00 FE 
09-Apr-2018 21:56:56.688 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:56.688 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 18 00 04 00 02 12 60 0D 01 00 32 02 21 74 00 03 2F 28 00 00 00 00 00 00 FE 
09-Apr-2018 21:56:56.688 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 18 00 04 00 02 12 60 0D 01 00 32 02 21 74 00 03 2F 28 00 00 00 00 00 00 FE 
09-Apr-2018 21:56:56.688 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 12 60 0D 01 00 32 02 21 74 00 03 2F 28 00 00 00 00 00 00 
09-Apr-2018 21:56:56.689 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:56.689 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:56.689 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:56.689 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class MULTI_INSTANCE
09-Apr-2018 21:56:56.689 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Received MULTI_INSTANCE command V2
09-Apr-2018 21:56:56.689 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Requested Command Class = METER (0x32)
09-Apr-2018 21:56:56.689 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Endpoint = 1, calling handleApplicationCommandRequest.
09-Apr-2018 21:56:56.689 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Received METER command V2
09-Apr-2018 21:56:56.690 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Meter: Type=Electric(1), Scale=W(2), Value=208.68
09-Apr-2018 21:56:56.690 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.690 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.690 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 1, command class = METER, value = 208.68
09-Apr-2018 21:56:56.690 [DEBUG] [nding.zwave.internal.converter.ZWaveMeterConverter] - Not the right scale E_KWh <> E_W
09-Apr-2018 21:56:56.690 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:meter_watts1 to 208.68 [DecimalType]
09-Apr-2018 21:56:56.690 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255
09-Apr-2018 21:56:56.782 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 04 00 02 12 60 0D 02 00 32 02 21 74 00 0E DF 30 00 00 00 00 00 00 18 
09-Apr-2018 21:56:56.788 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:56.788 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 18 00 04 00 02 12 60 0D 02 00 32 02 21 74 00 0E DF 30 00 00 00 00 00 00 18 
09-Apr-2018 21:56:56.788 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 18 00 04 00 02 12 60 0D 02 00 32 02 21 74 00 0E DF 30 00 00 00 00 00 00 18 
09-Apr-2018 21:56:56.788 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 12 60 0D 02 00 32 02 21 74 00 0E DF 30 00 00 00 00 00 00 
09-Apr-2018 21:56:56.788 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:56.789 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:56.789 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:56.789 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class MULTI_INSTANCE
09-Apr-2018 21:56:56.789 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Received MULTI_INSTANCE command V2
09-Apr-2018 21:56:56.789 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Requested Command Class = METER (0x32)
09-Apr-2018 21:56:56.789 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Endpoint = 2, calling handleApplicationCommandRequest.
09-Apr-2018 21:56:56.789 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Received METER command V2
09-Apr-2018 21:56:56.790 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Meter: Type=Electric(1), Scale=W(2), Value=974.64
09-Apr-2018 21:56:56.790 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.790 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.790 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 2, command class = METER, value = 974.64
09-Apr-2018 21:56:56.790 [DEBUG] [nding.zwave.internal.converter.ZWaveMeterConverter] - Not the right scale E_KWh <> E_W
09-Apr-2018 21:56:56.790 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:meter_watts2 to 974.64 [DecimalType]
09-Apr-2018 21:56:56.790 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255
09-Apr-2018 21:56:56.882 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 04 00 02 12 60 0D 01 00 32 02 21 64 00 45 A0 C7 00 F0 00 45 A0 BA 67 
09-Apr-2018 21:56:56.890 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:56.890 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 18 00 04 00 02 12 60 0D 01 00 32 02 21 64 00 45 A0 C7 00 F0 00 45 A0 BA 67 
09-Apr-2018 21:56:56.890 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 18 00 04 00 02 12 60 0D 01 00 32 02 21 64 00 45 A0 C7 00 F0 00 45 A0 BA 67 
09-Apr-2018 21:56:56.891 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 12 60 0D 01 00 32 02 21 64 00 45 A0 C7 00 F0 00 45 A0 BA 
09-Apr-2018 21:56:56.891 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:56.891 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:56.891 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:56.891 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class MULTI_INSTANCE
09-Apr-2018 21:56:56.891 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Received MULTI_INSTANCE command V2
09-Apr-2018 21:56:56.891 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Requested Command Class = METER (0x32)
09-Apr-2018 21:56:56.891 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Endpoint = 1, calling handleApplicationCommandRequest.
09-Apr-2018 21:56:56.892 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Received METER command V2
09-Apr-2018 21:56:56.892 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Meter: Type=Electric(1), Scale=kWh(0), Value=4563.143
09-Apr-2018 21:56:56.892 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.892 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.892 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 1, command class = METER, value = 4563.143
09-Apr-2018 21:56:56.892 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:meter_kwh1 to 4563.143 [DecimalType]
09-Apr-2018 21:56:56.893 [DEBUG] [nding.zwave.internal.converter.ZWaveMeterConverter] - Not the right scale E_W <> E_KWh
09-Apr-2018 21:56:56.893 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255
09-Apr-2018 21:56:56.982 [DEBUG] [wave.handler.ZWaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 18 00 04 00 02 12 60 0D 02 00 32 02 21 64 00 48 87 02 00 F0 00 48 86 C1 DB 
09-Apr-2018 21:56:56.990 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
09-Apr-2018 21:56:56.990 [DEBUG] [nhab.binding.zwave.internal.protocol.SerialMessage] - Assembled message buffer = 01 18 00 04 00 02 12 60 0D 02 00 32 02 21 64 00 48 87 02 00 F0 00 48 86 C1 DB 
09-Apr-2018 21:56:56.990 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Process Message = 01 18 00 04 00 02 12 60 0D 02 00 32 02 21 64 00 48 87 02 00 F0 00 48 86 C1 DB 
09-Apr-2018 21:56:56.990 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 02 12 60 0D 02 00 32 02 21 64 00 48 87 02 00 F0 00 48 86 C1 
09-Apr-2018 21:56:56.990 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Application Command Request (ALIVE:DONE)
09-Apr-2018 21:56:56.991 [DEBUG] [protocol.initialization.ZWaveNodeInitStageAdvancer] - NODE 2: Starting initialisation from DONE
09-Apr-2018 21:56:56.991 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@c568304 already registered
09-Apr-2018 21:56:56.991 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 2: Incoming command class MULTI_INSTANCE
09-Apr-2018 21:56:56.991 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Received MULTI_INSTANCE command V2
09-Apr-2018 21:56:56.991 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Requested Command Class = METER (0x32)
09-Apr-2018 21:56:56.991 [DEBUG] [otocol.commandclass.ZWaveMultiInstanceCommandClass] - NODE 2: Endpoint = 2, calling handleApplicationCommandRequest.
09-Apr-2018 21:56:56.991 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Received METER command V2
09-Apr-2018 21:56:56.992 [DEBUG] [ernal.protocol.commandclass.ZWaveMeterCommandClass] - NODE 2: Meter: Type=Electric(1), Scale=kWh(0), Value=4753.154
09-Apr-2018 21:56:56.992 [DEBUG] [ab.binding.zwave.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.992 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveMeterValueEvent
09-Apr-2018 21:56:56.992 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 2, command class = METER, value = 4753.154
09-Apr-2018 21:56:56.992 [DEBUG] [rg.openhab.binding.zwave.handler.ZWaveThingHandler] - NODE 2: Updating channel state zwave:device:f019eab0:node2:meter_kwh2 to 4753.154 [DecimalType]
09-Apr-2018 21:56:56.992 [DEBUG] [nding.zwave.internal.converter.ZWaveMeterConverter] - Not the right scale E_W <> E_KWh
09-Apr-2018 21:56:56.992 [DEBUG] [tocol.serialmessage.ApplicationCommandMessageClass] - NODE 17: Transaction not completed: node address inconsistent.  lastSent=17, incoming=255

[chris (Chris Jackson)]

I haven’t read all this thread to know what is, and what isn’t updating, but below is what the log looks like, and it seems that the binding is properly updating the state for all data it is receiving…

[sihui]

Here is a snippet

It looks like your multisensor is node 11, so please post the log entries for node 11.

[NOTORIOUS_VR]

It looks like your multisensor is node 11, so please post the log entries for node 11

Is that a separate action? Or just anything from NODE 11 from the (debug) ZWAVE log file?

[NOTORIOUS_VR]

I haven’t read all this thread to know what is, and what isn’t updating, but below is what the log looks like, and it seems that the binding is properly updating the state for all data it is receiving…

From what I can see in the panel (Basic or Paper UI), None of my motion, temp, door, multisensors are displaying anything for some reason.

I didn’t want to complicate my install/setup before finding out why my Z-wave switches and dimmers are working, but nothing else Z-wave is reporting data.

[sihui]

Or just anything from NODE 11 from the (debug) ZWAVE log file?

Anything from node 11, but even better: post the whole debug log, for example on pastebin or any other free service and link it here.

[NOTORIOUS_VR]

Anything from node 11, but even better: post the whole debug log, for example on pastebin or any other free service and link it here.

https://drive.google.com/open?id=1SRiaHUQAAfCOyc8dKXuhoIjmm563Ui5-

Thanks!

[sihui]

Not much in there for node 11 when feeding through the log viewer:

[NOTORIOUS_VR]

Not much in there for node 11 when feeding through the log viewer

Well that log viewer is cool! Thanks for linking that.

That said, is there something else to expect from a NODE? If it shows command received, it must have gotten that data from the sensor right?

As I said, it seems like all my sensors so far aren’t reporting anything in OH2. Although they’re bound and seemingly receiving commands.

In Domoticz the sensors are working flawlessly.

Is there a possibility the way the sensors were setup with my Z-wave interface through Domoticz could be causing the issue? I understood it really wasn’t up to the software since the NODES are bound to the interface and that is that. But maybe Domoticz and OH2 handle the initial connection differently and I have to completely reset my controller and wipe all the devices off?

Doesn’t make sense to me (and I hope I do not have to do that) if that were the case since OH does in fact see all my Z-wave devices correctly that are connected to my Z-wave controller.

[sihui]

If it shows command received

It does not show any values, though.

it seems like all my sensors so far aren’t reporting anything in OH2

By “all” you mean ALL???
Then you need to start from the basics:
Your items and sitemap setup is not clear to me, why aren’t you just linking one channel (let’s assume the motion channel of your multisensor) to a switch type item and see what happens? Uncomment all that other stuff …

Is the zwave binding running? Check via karaf console and do a bundle:list, you should see something like:
247 │ Active │ 80 │ 2.3.0.201804090748 │ ZWave Binding
Make sure you only have one zwave binding and it is in active state.

Then check your events.log, you should see state changes:
2018-04-11 07:57:02.828 [vent.ItemStateChangedEvent] - FibEye1_Motion_S changed from ON to OFF

Also check your userdata/zwave folder if your nodes did create an xml file.

[NOTORIOUS_VR]

It does not show any values, though.

Right, well that coincides with me being able to bind the sensors but not able to see any data from them

Why would it show CMD received but not have data associated with it though. Makes no sense. I know for a fact that the sensor works. I can turn down the OH2 VM and spin up Domoticz VM and instantly everything is working as it should once the Z-wave binding does all it’s network checks.

By “all” you mean ALL???

Then you need to start from the basics:

Your items and sitemap setup is not clear to me, why aren’t you just linking one channel (let’s assume the motion channel of your multisensor) to a switch type item and see what happens? Uncomment all that other stuff …

Admittedly the sitemap was generated for me by OH2 using the Home Builder. But the switches and sensors seem to show up correctly in the UI which is what I thought the sitemap was actually for. Mapping the “site” for Menus/Groups.

Items was also generated by the Home Builder web app, and switches dimmers that I’ve mapped/bound are working. I know I sound like a broken record, but you’re asking me if the z-wave binding is working but it must be for OH to see all my Nodes and for me to be able to change the state of the items that are working right? It is also clear in the logs it sees the Z-wave nodes/neighbours.

As for linking just one channel from a sensor, I did try that and had the same result. Zero Data.

I’ll do some more digging this weekend with the logs I suppose see if anything stands out.

Thanks for the help so far!

[sihui]

and switches dimmers that I’ve mapped/bound are working.

Good, this was not clear to me because of the “all”.

But the switches and sensors seem to show up correctly in the UI which is what I thought the sitemap was actually for.

Correct. But those will only show data if the channels of your things (devices) are correctly linked to the items.

Why would it show CMD received

Because you hit the refresh button in the UI? You need to see a “state update” like for your node 17.

As for linking just one channel from a sensor, I did try that and had the same result. Zero Data.

Did you follow my advice and link a switch type item? Or do you still link a contact type item? Contact won’t work, you need a switch type item for motion events.

Also make sure you have a xml file in your userdata/zwave folder for your node in question.

Good luck.

Edit: also make sure to remove the motion.map in your label for testing, you may add it back later …

[NOTORIOUS_VR]

Well just wanted to update everyone who chimed in to help.

I took a few hours on Sunday to completely blow up my OH2 install starting from scratch (this time in expert mode for the HABmin panel). And I only added the z-wave binding this time and nothing else.

That didn’t help my situation with my sensors. So I decided that I would try excluding them and including them again under OH2… That seemed to make them work the multisensor 6 is working flawless as of currently.

That gave me new drive to start to setup every z-wave device and properly map/bind them and build the sitemap from scratch.

So far so good. There are a few door sensors that don’t seem to report all data (ie. door contact works, but LUX and temp are not) so I will try the exclusion/inclusion with them as well.

Next setup is to get MQTT working on my setup as I have many reflashed Sonos switches throughout controlling various lights, and then start to make rules (this part I’m dreading the most, but I hope to be able to use Node Red for this as it seems like it will be much simpler that way and closer to the way Domoticz did it ie. visually) to start automating things.

Cheers!

[sihui]

Next setup is to get MQTT working

MQTT Binding (v1.11) Getting Started 101

After countless threads regarding initial configuration issues, here is a short guide on how to get started with MQTT, the MQTT binding and openHAB. This thread is a wiki article and can be improved by everyone. Please do! MQTT is a machine-to-machine (M2M)/“Internet of Things” connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport. A few resources first: Read all you ever need to know about MQTT in the MQTT Essentials The openHAB MQT…

Good luck and happy switching.

So I decided that I would try excluding them and including them again under OH2 … That seemed to make them work the multisensor 6 is working flawless as of currently.

Interesting: I did not expect that …

[NOTORIOUS_VR]

Good luck and happy switching.

NOTORIOUS_VR:

Thanks… I cannot seem to catch any luck with OH it seems… very frustrating experiences so far.

Setup the broker, installed the binding and configured…

Get the confirmation in the log as the guide in your link indicated.

018-04-17 19:05:08.210 [INFO ] [penhab.io.transport.mqtt.MqttService] - MQTT Service initialization completed.

2018-04-17 19:05:08.211 [INFO ] [t.mqtt.internal.MqttBrokerConnection] - Starting MQTT broker connection '<broker>'

But OH2 doesn’t actually seem to speak to the broker. I can toggle my switches using an explorer like MQTTlens just fine so I know the broker is working but for the life of me I cannot get OH to send the messages when I toggle the switch eg:

Switch   Kitchen_Light_Stove                "Kitchen Stove Light"           <light>         (Kitchen, gLight)                           { mqtt=">[broker:cmnd/sonoff-8153/power:command:*:default]" }

Even the test at the bottom of the guide you linked doesn’t work as it should (log never confirms the state change) for:

Switch MQTT_Test "Testing..." { mqtt="<[broker:testing/mqtt/topic:state:default], >[broker:testing/mqtt/back-topic:command:*:default]" }

[NOTORIOUS_VR]

Never mind… I found my own mistake…

in the cfg I left the default of it then clicked when I saw the command when I pasted it here and happened to look at the instructions in the header of the cfg.

changed from.url to broker.url and it started to work right away…

heh