Zooz ZSE40 4-in-1 sensor

billtylerjr · December 26, 2016, 7:26am

Has anyone gotten a new one these recently? It appears the manufacturer id has changed so its not being found in the database. I tried to add the xml to the database but it seem it cannot be taken with the manufacturer being added separately.

here is the xml that i got when adding it to openHab2:

ROUTING_SLAVE
SENSOR_NOTIFICATION
NOTIFICATION_SENSOR

0xfb37d2b5
7
4
0x27a
0x2101
0x2021
false
false
true
false
true
40000

ZWAVE_PLUS_INFO
VERSION
MANUFACTURER_SPECIFIC
DEVICE_RESET_LOCALLY
ASSOCIATION
ASSOCIATION_GROUP_INFO
POWERLEVEL
BATTERY
ALARM
SENSOR_MULTILEVEL
CONFIGURATION
WAKE_UP
FIRMWARE_UPDATE_MD

FIRMWARE_UPDATE_MD

1
1
2

ASSOCIATION_GROUP_INFO

1
1
1

1

ZWAVE_PLUS_INFO

1
1
2
1
6
0
0xc07
0xc07
true

SENSOR_MULTILEVEL

7
1
7

LUMINANCE

LUMINANCE
true

RELATIVE_HUMIDITY

RELATIVE_HUMIDITY
true

TEMPERATURE

TEMPERATURE
true

true

VERSION

2
1
2
LIB_SLAVE_ENHANCED
4.5
16.9
1

ALARM

4
1
4

BURGLAR

BURGLAR

3
8

false
true

POWERLEVEL

1
1
1
0
0

DEVICE_RESET_LOCALLY

1
1
1

MANUFACTURER_SPECIFIC

1
1
2
false
634
8225
8449

ASSOCIATION

2
1
2
1

BASIC

1
1
1
true

CONFIGURATION

1
1
1

SENSOR_BINARY

0
0
0
true

NO_OPERATION

1
1
1

BATTERY

1
1
1
100
false
true

WAKE_UP

2
1
2
1
43200
600
604800
43200
600
2016-12-26 05:54:54.489 UTC
true

1

1
Lifeline
0x1

BASIC
SENSOR_MULTILEVEL
ALARM
BATTERY
DEVICE_RESET_LOCALLY

1
3
4

2016-12-26 05:54:57.120 UTC
2016-12-26 05:54:55.529 UTC

chris · December 26, 2016, 12:09pm

I suspect that Zooz have got themselves their own manufacturer ID - I will add this to the database today (another user already emailed me about this a couple of days back - I’ve just been a bit slow to add it).

chris · December 26, 2016, 2:57pm

For the record -:

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/491

njcrawford · December 27, 2016, 2:37am

I’m interested in trying out the new entry, is there a build for OH1 with the newest Zwave database?

P.S. you guys are on the ball! I just received one of these with the new manufacturer ID for Christmas, and was coming here to report it. Not only has it been reported, but it’s already been added to the Zwave database!

billtylerjr · December 27, 2016, 4:18am

Awesome, thanks Chris.

njcrawford · December 28, 2016, 8:32pm

Now that I understand how to export devices from the database and do pull requests, I’ve created this pull request to add this device to OH1: https://github.com/openhab/openhab/pull/4946

chris · December 28, 2016, 10:24pm

Thanks.

naturalblaze · March 2, 2017, 3:29am

Has anyone gotten the PIR (motion) working for openHab2? I just got one of these these and I have everything reporting except the PIR. It doesn’t seem to report anything.

naturalblaze · March 2, 2017, 5:21pm

I figured it out. Looks like the Alarm (burglar) zwave:device:zstick-s2:node64:alarm_burglar and Binary Sensor zwave:device:zstick-s2:node64:sensor_binary are backwards. It does get recognized correctly as ZSE40 4-in-1 Sensor. So I don’t know if the confige file just has those backwards or what. It’s not that big of a deal. I just didn’t have an item for the tamper switch initially but when I added both I could see the alarm_burglar was triggering on motion. It doesn’t seem the tamper switch is triggering when I remove the back cover but not a show stopper on my end.

zzarbi · March 14, 2017, 10:40pm

Hi,

I’m new to openHab, I’ve been using Smartthings for similar Home Automation and I’m planning to migrate to openHab.
I’m trying to setup one Zooz ZSE40 Motion sensor and I’m at a dead end.
@chris mention he updated his DB with this new device in December 2016, I installed openHAB for linux following those steps http://docs.openhab.org/installation/linux.html (I pick the stable install). In other discussion Chris mention we just need to run an update to get the latest devices added to the zwave “DB”. But this doesn’t seem to cut it.

I also read I can install eclipse and develop bindings, I also follow the steps and got eclipse setup to develops bindings but there it’s missing the zwave binding.

I’m kinda lost… if anybody care to explain I would appreciate it.

PS: I was able to detect my device, but openHAB doesn’t recognize it (https://gist.github.com/zzarbi/4a68a39cd815ce3bd0cb70849643e19f)

The1Percent · July 3, 2017, 1:56am

I am having the exact same problem and not really sure what to do.

zzarbi · July 3, 2017, 2:12am

Basically you have to install the “beta” version and then you have access to more devices.

chris · July 3, 2017, 7:02am

Ok use V2.1 release - this should also contain the device…

The1Percent · July 4, 2017, 6:29am

Wow… that was easy. Literally apt-get upgrade openhab2.

Reboot…

Wait about 10 minutes

Login,

Presto!

Thanks!

will_stewart1a · February 19, 2018, 7:55pm

I was able to discover the existence of a “thing” at this node, but Openhab2 did not recognize it as a brand new Zooz 4-in-1 Sensor ZSE40, even when it looked at it as such.

2018-02-18 22:16:51.652 [DEBUG] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Checking zwave:vision_zse40_00_000
 
(other products checked...)

2018-02-18 22:16:51.694 [WARN ] [wave.discovery.ZWaveDiscoveryService] - NODE 18: Device discovery could not resolve to a thingType! 7FFFFFFF:7FFFFFFF:7FFFFFFF::0.0
2018-02-18 22:16:51.694 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing 'zwave:device:7efa0603:node18' to inbox.
2018-02-18 22:16:51.695 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller start inclusion - mode 2
2018-02-18 22:16:51.695 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Setting controller into INCLUSION mode, highPower:true networkWide:false.

What I could pull from the json was limited;

  "zwave:device:7efa0603:node18": {
    "class": "org.eclipse.smarthome.core.thing.internal.ThingImpl",
    "value": {
      "label": "Z-Wave Node 18",
      "bridgeUID": {
        "segments": [
          "zwave",
          "serial_zstick",
          "7efa0603"
        ]
      },
      "channels": [],
      "configuration": {
        "properties": {}
      },
      "properties": {
        "zwave_class_basic": "ROUTING_SLAVE",
        "zwave_class_generic": "SENSOR_NOTIFICATION",
        "zwave_frequent": "false",
        "zwave_neighbours": "1,2,3,12,13,14,16,17",
        "zwave_nodeid": "18",
        "zwave_version": "0.0",
        "zwave_listening": "false",
        "zwave_routing": "true",
        "zwave_wakeup_time": "2018-02-19T15:44:06Z",
        "zwave_beaming": "true",
        "zwave_class_specific": "NOTIFICATION_SENSOR"
      },
      "uid": {
        "segments": [
          "zwave",
          "device",
          "7efa0603",
          "node18"
        ]
      },
      "thingTypeUID": {
        "segments": [
          "zwave",
          "device"
        ]
      },
      "location": "Master Bathroom"
    }
  },

I’ve waited a day to let this battery powered device work it’s way through the steps, and have been waking it up frequently, though to no avail. Is there something else I can do?

chris · February 19, 2018, 7:58pm

The device has not been initialised at all - try waking it up a few times to see if it initialised.

will_stewart1a · February 20, 2018, 12:20am

Thanks, a few dozen wake-ups succeeded in initializing the node;

2018-02-19 13:49:12.888 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer - NEIGHBORS: Transaction complete (GetRoutingInfo:Request) success(true)
2018-02-19 13:49:12.888 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer - checking initialisation queue. Queue size 1.
2018-02-19 13:49:12.888 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer - message removed from queue. Queue size 0.
2018-02-19 13:49:12.888 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer - NEIGHBORS: queue length(0), free to send(true)
2018-02-19 13:49:12.888 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer: loop - NEIGHBORS try 1: stageAdvanced(false)
2018-02-19 13:49:12.888 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer - advancing to DONE
2018-02-19 13:49:12.889 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
2018-02-19 13:49:12.889 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer: loop - DONE try 0: stageAdvanced(true)
2018-02-19 13:49:12.889 [DEBUG] [l.initialization.ZWaveNodeSerializer] - NODE 18: Serializing to file /var/lib/openhab2/zwave/node18.xml
2018-02-19 13:49:12.891 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Node advancer: Initialisation complete!
2018-02-19 13:49:12.891 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInitializationStateEvent
2018-02-19 13:49:12.891 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 10ms/4565ms.
2018-02-19 13:49:13.891 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: No more messages, go back to sleep
2018-02-19 13:49:13.891 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 18: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION

However, I can’t get HABmin to recognize it is now initialized, it still thinks it is an unknown device, even after restarting OH2, waiting for it to work through any new configurations, and refreshing HABmin multiple times.

The node .xml is here

The node has been reporting motion as alarms, which is new to me;

2018-02-19 19:06:05.632 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:WAIT)
2018-02-19 19:06:05.632 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class ALARM
2018-02-19 19:06:05.632 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Received ALARM command V4
2018-02-19 19:06:05.632 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Process NOTIFICATION_REPORT V4
2018-02-19 19:06:05.632 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: NOTIFICATION report - 7 = 255, event=8, status=255
2018-02-19 19:06:05.632 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Alarm Type = BURGLAR (7)
2018-02-19 19:06:05.632 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-02-19 19:06:05.632 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-02-19 19:06:05.632 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255

HABmin normally updates it’s information automatically, what do I need to do to have it recognize this node?

chris · February 20, 2018, 7:40am

What does it report exactly?

will_stewart1a · February 20, 2018, 1:11pm

Multiple restarts of OH2 seemed to gradually infuse the initialization into all the nooks and crannies, so HABmin now does see it as a 4-in-1 sensor, and I am able to make item declarations and linkages.

However, your question has an interesting answer. There were 8 channels available, with the first two channels listed in the HABmin display as binary sensors. The motion sensor came further down near the end of the list. At first, no motion events were forthcoming when I first began testing, so I added an item and linkage for each of the binary sensors. Intriguingly, those linkages both show up in both the first and second binary sensor channels, and the first channel is now marked “Motion” on the HABmin display. The previously labeled Motion channel now says Motion Alarm. As the channel listing/linkages now stand;

How they report in HABmin;

The OH log shows the following when someone moves past the sensor;

2018-02-20 07:47:05.201 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DONE)
2018-02-20 07:47:05.201 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
2018-02-20 07:47:05.201 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@2d94a4e already registered
2018-02-20 07:47:05.201 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class BASIC
2018-02-20 07:47:05.201 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Received Basic Request
2018-02-20 07:47:05.201 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic Set sent to the controller will be processed as Basic Report
2018-02-20 07:47:05.201 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 18: Basic report, value = 0xFF
2018-02-20 07:47:05.201 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
2018-02-20 07:47:05.201 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-02-20 07:47:05.202 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
2018-02-20 07:47:05.202 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Updating channel state zwave:device:7efa0603:node18:sensor_binary to ON [OnOffType]
2018-02-20 07:47:05.202 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 2: Transaction not completed: node address inconsistent.  lastSent=2, incoming=255
2018-02-20 07:47:05.220 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 12 0A 71 05 07 FF 00 FF 07 08 00 00 8F 
2018-02-20 07:47:05.221 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-02-20 07:47:05.221 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 12 0A 71 05 07 FF 00 FF 07 08 00 00 8F 
2018-02-20 07:47:05.221 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 12 0A 71 05 07 FF 00 FF 07 08 00 00 8F 
2018-02-20 07:47:05.221 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 12 0A 71 05 07 FF 00 FF 07 08 00 00 
2018-02-20 07:47:05.221 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Application Command Request (ALIVE:DONE)
2018-02-20 07:47:05.221 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 18: Starting initialisation from DONE
2018-02-20 07:47:05.221 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@2d94a4e already registered
2018-02-20 07:47:05.221 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 18: Incoming command class ALARM
2018-02-20 07:47:05.221 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Received ALARM command V4
2018-02-20 07:47:05.221 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Process NOTIFICATION_REPORT V4
2018-02-20 07:47:05.221 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: NOTIFICATION report - 7 = 255, event=8, status=255
2018-02-20 07:47:05.222 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 18: Alarm Type = BURGLAR (7)
2018-02-20 07:47:05.222 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-02-20 07:47:05.222 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-02-20 07:47:05.222 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 18: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-02-20 07:47:05.222 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-02-20 07:47:05.222 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 8, type OnOffType
2018-02-20 07:47:05.222 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-02-20 07:47:05.222 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 8, type OnOffType

The event.log shows;

2018-02-20 07:47:05.202 [vent.ItemStateChangedEvent] - MasterBathroomBinarySensor1 changed from OFF to ON
2018-02-20 07:47:05.202 [vent.ItemStateChangedEvent] - MasterBathroomBinarySensor2 changed from OFF to ON
2018-02-20 07:47:17.518 [vent.ItemStateChangedEvent] - MasterBathroomBinarySensor1 changed from ON to OFF
2018-02-20 07:47:17.518 [vent.ItemStateChangedEvent] - MasterBathroomBinarySensor2 changed from ON to OFF
2018-02-20 07:47:44.007 [vent.ItemStateChangedEvent] - ntp_ntp_local_dateTime changed from 2018-02-20T07:46:44.005-0500 to 2018-02-20T07:47:44.006-0500
2018-02-20 07:47:44.007 [vent.ItemStateChangedEvent] - ntp_ntp_local_string changed from 2018-02-20 07:46:44 EST to 2018-02-20 07:47:44 EST

As it appears that the product description needs tweaking, I plan on brushing up on my xml, digging into the product information (found this), brushing up on git pulls, and then submitting an update to this product definition. It may be helpful for someone to check my work before I submit (with guests coming soon for the next two weeks, it won’t be before they leave). For now I can make it work with what is currently reported (and clearly those who have these sensors have discovered a workaround).

robster_mn · October 31, 2018, 1:04am

I just bought one of these and got it added using using HabMin? Question how do I get the new device added to the items or things files? So I can pull that into the sitemaps.

Sorry for the noob question?

Thanks for any help