I’ve tried to add a ZSE43, I can see that it’s adopted and the XML file is properly created, but it’s not recognized. I looked in the Zwave database and I can see it’s there. What do I need to do?
Ira
Do the reference numbers match? (027A) 7000:E002
As far as I can tell it all matches. I can attach the XML file here if you want.
network_ece4041c__node_77.xml (12.3 KB)
And before I forget, thanks for looking.
So the device ID is E003, not E002, hence the problem. If you have DB access, verify everything else is the same as your device. If yes, with write access (open ticket with attain) you can simply add to the TYPE 7000:E003 to that line on the overview page. If no, you will need to create a new device as explained in the blog @jswim788 had posted.
Bob
I can’t seem to log in. I did send a message asking for permissions, but I don’t seem to have it yet.
And now I feel really stupid, I seem to have got the number wrong, I should have said ZSE43, not ZSE42 which I think is why you get the different version and I thought it was the same. So sorry for the error.
No Worries.
The problem with the ZSE43 is that it is modified, but no review has been requested. Assuming that was an oversight, I’ll mark for review. If there is a problem (once included in the binding) it might need to be modified in the future.
Bob
Thank you. If there is anything I can do to help, just ask.
This device caught my eye yesterday when I was looking at the water device ZSE42. I had been looking to replace my ecolink tilt 2.5 (500 series) with a 700 level battery device. Once it is working, I’d be interested in your feedback.
Bob
Well, it shows up now, but it seems like only some of the events are implemented. I can see the zwave messages when I turn on debug and tilt the sensor but I got no events telling me the sensor was tilted.
I did go ahead and buy a couple. I did need to change the DB alarms to get the tilt to report. It should be in the next DB update (1779). I’ve only had them for a day, but seem okay so far.
Bob
I just purchased this with the ZEN43 to move away from MQTT for my garage door. I see the events in the logs as well, but also none of the items change states (aside from the battery).
Well, it shows up now, but it seems like only some of the events are implemented. I can see the zwave messages when I turn on debug and tilt the sensor but I got no events telling me the sensor was tilted.
Just a little more information, and a question if anyone actually got this working???
In the debug logs, when it switches to closed, I get Notification event 23 (see logs below)
2022-11-22 16:34:59.293 [DEBUG] [nal.protocol.ZWaveTransactionManager] - processReceiveMessage input 0<>128 : Message: class=ApplicationCommandHandler[4], type=Request[0], dest=28, callback=0, payload=00 1C 09 71 05 00 00 00 FF 06 17 00
2022-11-22 16:34:59.294 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=28, callback=0, payload=00 1C 09 71 05 00 00 00 FF 06 17 00
2022-11-22 16:34:59.295 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-11-22 16:34:59.296 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Application Command Request (ALIVE:DONE)
2022-11-22 16:34:59.297 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: resetResendCount initComplete=true isDead=false
2022-11-22 16:34:59.297 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2022-11-22 16:34:59.298 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: SECURITY not supported
2022-11-22 16:34:59.299 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 28: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2022-11-22 16:34:59.299 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: NOTIFICATION report - 0 = 0, event=23, status=255, plen=0
2022-11-22 16:34:59.300 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: Alarm Type = ACCESS_CONTROL (0)
2022-11-22 16:34:59.301 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2022-11-22 16:34:59.301 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2022-11-22 16:34:59.302 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter processing NOTIFICATION
2022-11-22 16:34:59.303 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter NOTIFICATION event is 23, type OnOffType
2022-11-22 16:34:59.303 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter NOTIFICATION event is 23, channel alarm_access is not implemented.
2022-11-22 16:34:59.304 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter processing NOTIFICATION
2022-11-22 16:34:59.304 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter NOTIFICATION event is 23, type OnOffType
2022-11-22 16:34:59.305 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Commands processed 1.
2022-11-22 16:34:59.306 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@751e15e5.
2022-11-22 16:34:59.306 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
And, when it switches to open, I get Notification event 22 (see this batch of logs)
2022-11-22 16:34:57.387 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Received msg (0): Message: class=ApplicationCommandHandler[4], type=Request[0], dest=28, callback=0, payload=00 1C 09 71 05 00 00 00 FF 06 16 00
2022-11-22 16:34:57.388 [DEBUG] [nal.protocol.ZWaveTransactionManager] - lastTransaction null
2022-11-22 16:34:57.388 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Application Command Request (ALIVE:DONE)
2022-11-22 16:34:57.389 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: resetResendCount initComplete=true isDead=false
2022-11-22 16:34:57.390 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: Incoming command class COMMAND_CLASS_ALARM, endpoint 0
2022-11-22 16:34:57.391 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 28: SECURITY not supported
2022-11-22 16:34:57.391 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 28: Received COMMAND_CLASS_ALARM V8 NOTIFICATION_REPORT
2022-11-22 16:34:57.392 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: NOTIFICATION report - 0 = 0, event=22, status=255, plen=0
2022-11-22 16:34:57.393 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 28: Alarm Type = ACCESS_CONTROL (0)
2022-11-22 16:34:57.393 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2022-11-22 16:34:57.394 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 28: Got a value event from Z-Wave network, endpoint=0, command class=COMMAND_CLASS_ALARM, value=255
2022-11-22 16:34:57.395 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter processing NOTIFICATION
2022-11-22 16:34:57.395 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter NOTIFICATION event is 22, type OnOffType
2022-11-22 16:34:57.396 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter NOTIFICATION event is 22, channel alarm_access is not implemented.
2022-11-22 16:34:57.397 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter processing NOTIFICATION
2022-11-22 16:34:57.397 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 28: Alarm converter NOTIFICATION event is 22, type OnOffType
2022-11-22 16:34:57.398 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Commands processed 1.
2022-11-22 16:34:57.399 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 28: Checking command org.openhab.binding.zwave.internal.protocol.ZWaveCommandClassPayload@15055d29.
2022-11-22 16:34:57.399 [DEBUG] [nal.protocol.ZWaveTransactionManager] - Transaction completed - outstandingTransactions 0
The Binary Sensor channel remains “Triggered” no matter what.
The Alarm (Access) channel remains “Off”
The Alarm (Burglar) channel remains “Off”
The Battery Level remains at 100%
First are you talking about the ZSE43? I see a reference to ZEN16 in your post? If yes, I had two working for some time, but removed them recently as the battery life was not what I expected for 700 series device. Anyway what version of OH are you on? My guess is that you need to try a newer binding. There was a change right around when OH3.3 was released and may only be in OH3.4 milestones (or snapshots)
edit: there should be a sensor door channel see above
Little bit of a tangent here, but check with Zooz support on them if you haven’t already. I have one of their 700 series temperature sensors that went through batteries quickly and reported wildly fluctuating values. They sent me a firmware update that has helped considerably. Still testing, but much better than before.
They did send me a firmware upgrade, but I have not upgraded yet. Good to hear it helps.
Sorry, that was a typo, I’ll edit the previous post.
I’m on v3.3.0. I don’t have a sensor door channel, I’ll see about updating to v3.4 M4 and see if that helps. Thanks for the response!
ETA: Thanks, updating to 3.4 M4 worked.
I was happy to see this thread that ZSE43 work on 3.4 M4 so I ordered three of three of them. It paired perfectly, but I’m struggling to get the tilt to report as expected. I’m on 3.4 M5 and I use a text file for my items.
When I tilt and then return the sensor I get the following in my Z-wave logs:
11:14:25.160 70
RX REQ ApplicationCommandHandler ALARM_REPORT V1 UNKNOWN[00] V1LEVEL=0 ACCESS_CONTROL EVENT=23 0 /128
11:14:25.300 70
RX REQ ApplicationCommandHandler BATTERY_REPORT 76% 0 /128
11:14:25.309 70
STATE UPDATE zwave:device:ZWave:node70:battery-level 76 [DecimalType]
11:14:26.757 70
RX REQ ApplicationCommandHandler ALARM_REPORT V1 UNKNOWN[00] V1LEVEL=0 ACCESS_CONTROL EVENT=22 0 /128
At the same time my openhab.log shows the device battery updating:
2022-12-04 11:14:07.296 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'FF_Garage_Door_Front_Battery' changed from 100 to 92
2022-12-04 11:14:25.312 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'FF_Garage_Door_Front_Battery' changed from 92 to 76
Here are my entries in my items file:
Switch FF_Garage_Door_Front_Sensor "Garage Door Front [%s]" <garagedoor> (FF_Garage, gDoor) {channel="zwave:device:ZWave:node70:sensor_binary"}
Number FF_Garage_Door_Front_Battery "Garage Door Front Battery [%d %%]" <batterylevel> (gBattery) {channel="zwave:device:ZWave:node70:battery-level"}
Switch FF_Garage_Door_Front_Burgler "Garage Door Front Burgler [%s]" <siren> (FF_Garage, gAlarm) {channel="zwave:device:ZWave:node70:alarm_access"}
Switch FF_Garage_Door_Front_Alarm "Garage Door Front Alarm [%s]" <siren> (FF_Garage, gAlarm) {channel="zwave:device:ZWave:node70:alarm_burglar"}
Thank you in advance!
Event 22 is Access Control (0x6) - Door State - Window/door is open (0x16),
event 23 is Access Control (0x6) - Door State - Window/door is closed (0x17).
Device definition (Z-Wave database):
Mapping is wrong or Z-Wave binding doesn’t support notification Access Control/Door State.
Two things
1 Referring to the picture by @Ap15e Use the door state channel.
2. Contact Zooz about a firmware upgrade to 1.2. My device was running through batteries by constantly reporting battery status.