Nexia DB100Z and OpenHab2 Zwave Binding

[chris (Chris Jackson)]

Looking at the database, there should be a channel called Power Management Notification - this is an alarm channel, so I guess it is the doorbell?

The database could obviously do with improving for this device (for starters renaming the alarm if this is really the doorbell alarm). The manual attached to the database is also rather unhelpful.

[jgreene (Joe Greene)]

Ok weird I had to click see more in PaperUI to see the PowerManagementNotiffication channel

[chris (Chris Jackson)]

Maybe that’s a bug in PaperUI? There’s nothing in the way this channel is defined that should prevent it from being listed as a channel.

[jgreene (Joe Greene)]

I would be inclined to agree with that…

[jmckenna (James McKenna)]

Any luck with this device? I just set it up today and I am getting no updates on the alarm channel. In the log I see “channel notification_power_management is not implemented”:

2018-05-28 19:04:46.277 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 55 0A 71 05 00 00 00 FF 08 00 00 00 37
2018-05-28 19:04:46.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=85, callback=0, payload=00 55 0A 71 05 00 00 00 FF 08 00 00 00
2018-05-28 19:04:46.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage past lock Message: class=ApplicationCommandHandler[4], type=Request[0], dest=85, callback=0, payload=00 55 0A 71 05 00 00 00 FF 08 00 00 00
2018-05-28 19:04:46.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=85, callback=0, payload=00 55 0A 71 05 00 00 00 FF 08 00 00 00
2018-05-28 19:04:46.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2018-05-28 19:04:46.278 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 85: Application Command Request (ALIVE:DONE)
2018-05-28 19:04:46.278 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 85: resetResendCount initComplete=true isDead=false
2018-05-28 19:04:46.278 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 85: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2018-05-28 19:04:46.278 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 85: SECURITY not supported
2018-05-28 19:04:46.279 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 85: Received COMMAND_CLASS_ALARM V4 NOTIFICATION_REPORT
2018-05-28 19:04:46.279 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 85: NOTIFICATION report - 0 = 0, event=0, status=255, plen=0
2018-05-28 19:04:46.279 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 85: Alarm Type = POWER_MANAGEMENT (0)
2018-05-28 19:04:46.279 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-05-28 19:04:46.279 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 85: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-05-28 19:04:46.279 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 85: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255
2018-05-28 19:04:46.279 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-05-28 19:04:46.279 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, type OnOffType
2018-05-28 19:04:46.279 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 0, channel notification_power_management is not implemented.
2018-05-28 19:04:46.279 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 85: Commands processed 1.
2018-05-28 19:04:46.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 85: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@768b28a3.
2018-05-28 19:04:46.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-28 19:04:46.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
2018-05-28 19:04:46.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty
2018-05-28 19:04:46.280 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 0 out at start

[jmckenna (James McKenna)]

I updated the database so that channel type is now alarm_raw instead of notification_power_management. I made the change locally in my jsondb and then created a rule like @feens (Doorbell serial port trigger). Things seem to be working now.

The one thing I don’t like about this sensor is that if you press the doorbell quickly, it doesn’t always pickup the event. That’s the fault of the device though.

[feens (Trevor)]

@jmckenna @chris how do you use the alarm_raw item with my rule? The change to that broke things for me since updating OH and thus the Zwave binding.

[sihui]

@feens

how do you use the alarm_raw

A quick forum search found:

Zwave - Yale YRD220 Lock

Here is my current rule for parsing alarm_raw. My locks (Schlage BE469) do not update the lock_door channel, so I use alarm_raw to update the items linked to lock_door, and base rules off of that item’s state. Maybe all locks behave this way? You’ll find several examples of using the JSONPATH transform to parse the data in the lambda. This can be tricky though, because JSONPATH will throw an exception if the element name you are searching for does not exist in the JSON. I haven’t had any issues…

[chris (Chris Jackson)]

@feens

The change to that broke things for me

What change are you referring to? I’m not aware of any recent changes to the alarm_raw channel.

[feens (Trevor)]

@chris

@jmckenna

I updated the database so that channel type is now alarm_raw instead of notification_power_management

@sihui that’s actually the place I started but couldn’t get it to work. There doesn’t seem to be much documentation on the Alarm types.

[chris (Chris Jackson)]

Ok, that was 18 months ago

@feens

There doesn’t seem to be much documentation on the Alarm types.

Most alarms are simple Contact or OnOff types so don’t really require much documentation to use. The alarm_raw is a bit different in that it will dump information that comes from the device. This can change depending on the device, but it is provided as a simple JSON string that you would need to decode in the rule.

[feens (Trevor)]

@chris

Ok, that was 18 months ago

Ya, I’m updating all of my OH setup now. Obviously that change is supposed to make the setup more obvious than using the power management type. Is it possible that I can still use the same rule and just switch the item name, or is there an easy way to see what the raw response I get back is?

[chris (Chris Jackson)]

@feens

Is it possible that I can still use the same rule

I’m not sure what the rule is, but I guess it’s using a channel that doesn’t exist, so probably not.

What channel are you using and how is it configured?

[feens (Trevor)]

Sorry, the rule was linked to above by @jmckenna. I originally wrote it. Basically it just checked the power management status changing to ON. So now I somehow need to check if an event occurred but I’m not sure what to look for.

[chris (Chris Jackson)]

What is the channel type for your old channel?

[feens (Trevor)]

@jmckenna

notification_power_management

… something else I’m missing?

[chris (Chris Jackson)]

@feens

… something else I’m missing?

Sorry - I missed that as I’ve not read back through all this post looking for this bit of hidden information.

[jmckenna (James McKenna)]

@jmckenna

I made the change locally in my jsondb

I don’t think I actually made any changes to the database. Just locally. I see the database was updated today though. The Power Management Notification item links as a number. Here is an example rule:

rule "Doorbell received alarm"
when
Item Doorbell_Notify changed to 1
then
    logInfo("outside", "Rule: Doorbell received alarm - {}", Doorbell_Notify)

    createTimer(now.plusSeconds(15))[|
        Doorbell_Notify.postUpdate(0)
    ]
end

[sihui]

@jmckenna

I see the database was updated today though.

I did just the Overview, Inclusion and Exclusion information.

[sihui]

@jmckenna

Just locally.

Unfortunately this does not benefit to other users.