New devices for Z-Wave database

Hello @chris,
I’ve recently created 2 new devices in z-wave database HomeSeer HS-MS100+ and HS-LS100+. Could you review if I missed anything and let me know for future reference?
Also is there any timelines of when I should expect to see them in latest snapshot?
I’m planing to add move devices once there 2 are fine.

Sure - I’ll take a look tomorrow and do a binding update then, so they should be available tomorrow if it is all ok…

Thanks @chris . I see new thing in the database after upgrading to a latest snapshot. However Openhab still can’t identify it.
2018-03-02 21:58:28.049 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Device discovery could not resolve to a thingType! 000C:0201:0009::1.1
2018-03-02 21:58:28.102 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 8: Device discovery could not resolve to a thingType! 000C:0201:000A::1.2

Am I missing some step?

Are you sure you are using the latest snapshot? The updates are definitely in the latest version according to Github PR.

Here is my current version:

                      __  _____    ____      

____ ____ ___ ____ / / / / | / __ )
/ __ / __ / _ / __ / // / /| | / __ |
/ /
/ / // / __/ / / / __ / ___ |/ // /
_/ ./_// /// /// |/_____/
/_/ 2.3.0-SNAPSHOT
Build #1221

But I don’t see that it’s checking homeseer_hsls100_0_0

xxx@ubuntu-openhab-1:~$ cat /var/log/openhab2/openhab.log | grep homeseer
2018-03-03 10:20:00.337 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:homeseer_ezmotionexpress_00_000
2018-03-03 10:20:00.339 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:homeseer_ezmotionexpress_00_000
2018-03-03 10:20:00.396 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:homeseer_ezmultipli_00_000
2018-03-03 10:20:00.567 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:homeseer_hswd100_00_000
2018-03-03 10:20:01.604 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:homeseer_hsds100_00_000
2018-03-03 10:20:02.024 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:homeseer_hspa100_00_000
2018-03-03 10:20:02.113 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 5: Checking zwave:homeseer_hsws100_00_000

Sorry - I should have said - are you sure you’re running the latest snapshot of the zwave binding. Probably you are, but please check as the file is in the repo. It’s possible that Karaf has cached the files (it normally does this) and maybe it’s not updated.

The format looks ok (no errors in the validation) so I can’t see why it wouldn’t be included.

I see this file in add-on repository on my openhab server

/usr/share/openhab2/addon/openhab-addons-2.3.0-SNAPSHOT.kar

ls -l | grep homeseer

-rw-rw-r-- 1 pilot staff 10343 2 Mar 23:58 homeseer_ezmotionexpress_0_0.xml
-rw-rw-r-- 1 pilot staff 7951 2 Mar 23:58 homeseer_ezmultipli_0_0.xml
-rw-rw-r-- 1 pilot staff 6324 2 Mar 23:58 homeseer_hsds100_0_0.xml
-rw-rw-r-- 1 pilot staff 9053 2 Mar 23:58 homeseer_hsls100_0_0.xml
-rw-rw-r-- 1 pilot staff 7100 2 Mar 23:58 homeseer_hsms100_0_0.xml
-rw-rw-r-- 1 pilot staff 1463 2 Mar 23:58 homeseer_hspa100_0_0.xml
-rw-rw-r-- 1 pilot staff 4934 2 Mar 23:58 homeseer_hswd100_0_0.xml
-rw-rw-r-- 1 pilot staff 12171 2 Mar 23:58 homeseer_hswd200_0_0.xml
-rw-rw-r-- 1 pilot staff 3291 2 Mar 23:58 homeseer_hsws100_0_0.xml

Is there any way to clear Karaf cache? I restarted Openhab several times - no luck.

Log on to the console and check what version is running (bundle:list | grep zwave). If there are multiple versions, then uninstall the one you don’t want and the other should start.

If it is running the right version, then I’d check the log on startup to see if it’s being loaded, or if there’s a problem loading this file. It looks ok here, but maybe there’s something wrong still…

It worked after doing (bundle:update id).
Should I do it every time after apt-get upgrade? Is there any way to automate it?

I’m wondering if it’s my issue only, but after updating to latest snapshot and re-creating all ZWave devices I noticed that my Motion sensor HomeSeer HS-MS100+ is not working. I’m getting alarms but item (switch) state is not changing at all.

2018-10-04 19:52:00.416 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 1E 09 71 05 00 00 00 FF 07 09 00 66

2018-10-04 19:52:00.417 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 09 71 05 00 00 00 FF 07 09 00

2018-10-04 19:52:00.417 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 09 71 05 00 00 00 FF 07 09 00

2018-10-04 19:52:00.418 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 101: [WAIT_DATA] priority=Controller, requiresResponse=true, callback: 0

2018-10-04 19:52:00.418 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Application Command Request (ALIVE:REQUEST_NIF)

2018-10-04 19:52:00.418 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: Incoming command class COMMAND_CLASS_ALARM, endpoint 0

2018-10-04 19:52:00.418 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: SECURITY not supported

2018-10-04 19:52:00.419 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 30: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT

2018-10-04 19:52:00.420 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: NOTIFICATION report - 0 = 0, event=9, status=255, plen=0

2018-10-04 19:52:00.421 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: Alarm Type = BURGLAR (0)

2018-10-04 19:52:00.421 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got an event from Z-Wave network: ZWaveAlarmValueEvent

2018-10-04 19:52:00.422 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255

2018-10-04 19:52:00.422 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 30: Alarm converter processing NOTIFICATION

2018-10-04 19:52:00.423 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 30: Alarm converter NOTIFICATION event is 9, type OnOffType

2018-10-04 19:52:00.423 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Commands processed 1.

2018-10-04 19:52:00.424 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6b23e65b.

2018-10-04 19:52:00.424 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@6b23e65b.

2018-10-04 19:52:00.425 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1

2018-10-04 19:52:00.425 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1

2018-10-04 19:52:00.425 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-10-04 19:52:00.425 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2018-10-04 19:52:00.450 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 1E 09 71 05 00 00 00 FF 07 09 00 66

2018-10-04 19:52:00.452 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 09 71 05 00 00 00 FF 07 09 00

2018-10-04 19:52:00.452 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 09 71 05 00 00 00 FF 07 09 00

2018-10-04 19:52:00.453 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 101: [WAIT_DATA] priority=Controller, requiresResponse=true, callback: 0

2018-10-04 19:52:00.453 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Application Command Request (ALIVE:REQUEST_NIF)

2018-10-04 19:52:00.454 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: Incoming command class COMMAND_CLASS_ALARM, endpoint 0

2018-10-04 19:52:00.454 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: SECURITY not supported

2018-10-04 19:52:00.455 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 30: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT

2018-10-04 19:52:00.455 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: NOTIFICATION report - 0 = 0, event=9, status=255, plen=0

2018-10-04 19:52:00.455 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: Alarm Type = BURGLAR (0)

2018-10-04 19:52:00.456 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got an event from Z-Wave network: ZWaveAlarmValueEvent

2018-10-04 19:52:00.457 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255

2018-10-04 19:52:00.457 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 30: Alarm converter processing NOTIFICATION

2018-10-04 19:52:00.458 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 30: Alarm converter NOTIFICATION event is 9, type OnOffType

2018-10-04 19:52:00.458 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Commands processed 1.

2018-10-04 19:52:00.459 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@59d7179d.

2018-10-04 19:52:00.459 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@59d7179d.

2018-10-04 19:52:00.460 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1

2018-10-04 19:52:00.460 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1

2018-10-04 19:52:00.460 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-10-04 19:52:00.461 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

2018-10-04 19:52:02.011 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 1E 09 71 05 00 00 00 FF 07 09 00 66

2018-10-04 19:52:02.012 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 09 71 05 00 00 00 FF 07 09 00

2018-10-04 19:52:02.013 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=30, callback=0, payload=00 1E 09 71 05 00 00 00 FF 07 09 00

2018-10-04 19:52:02.014 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction TID 101: [WAIT_DATA] priority=Controller, requiresResponse=true, callback: 0

2018-10-04 19:52:02.014 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Application Command Request (ALIVE:REQUEST_NIF)

2018-10-04 19:52:02.015 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: Incoming command class COMMAND_CLASS_ALARM, endpoint 0

2018-10-04 19:52:02.016 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 30: SECURITY not supported

2018-10-04 19:52:02.017 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 30: Received COMMAND_CLASS_ALARM V5 NOTIFICATION_REPORT

2018-10-04 19:52:02.018 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: NOTIFICATION report - 0 = 0, event=9, status=255, plen=0

2018-10-04 19:52:02.018 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 30: Alarm Type = BURGLAR (0)

2018-10-04 19:52:02.019 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got an event from Z-Wave network: ZWaveAlarmValueEvent

2018-10-04 19:52:02.019 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 30: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_ALARM, value = 255

2018-10-04 19:52:02.020 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 30: Alarm converter processing NOTIFICATION

2018-10-04 19:52:02.020 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 30: Alarm converter NOTIFICATION event is 9, type OnOffType

2018-10-04 19:52:02.021 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Commands processed 1.

2018-10-04 19:52:02.021 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@155f0da9.

2018-10-04 19:52:02.022 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 30: Command NOT verified org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@155f0da9.

2018-10-04 19:52:02.022 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1

2018-10-04 19:52:02.022 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 1

2018-10-04 19:52:02.023 [DEBUG] [nal.protocol.ZWaveTransactionManager] - ZWaveReceiveThread queue empty

2018-10-04 19:52:02.023 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction SendNextMessage 1 out at start. Holdoff false.

What is “switch state”? What function does this provide? Normally for a motion sensor, there is an alarm_motion channel, and often an alarm_tamper channel. Some have temperature or other sensors - what is the switch state linked to?

Sorry for late response. What I mean is that I have an item with type of Switch which I’m linking to alarm_burglar channel of motion sensor. It was working before, but after latest upgrade it’s not changing state of my switch when motion detected. However as per my log I can see motion detection event coming from sensor.