[ST EDGE] Z-Wave Sensor Driver Channel - including specific Ecolink, FortrezZ, HomeSeer, Monoprice and Zooz models

──────────────────────────────────────────────────────────────────────────────────
 #   Driver Id                             Name
──────────────────────────────────────────────────────────────────────────────────
 
 9     Z-Wave Sensor
 
──────────────────────────────────────────────────────────────────────────────────
? Select a driver. 9
connecting... connected
2023-07-03T19:01:24.909256590+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2023-07-03T19:01:24.911725507+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> received Z-Wave command: {args={value=255}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="NONE", payload="\xFF", src_channel=0, version=1}
2023-07-03T19:01:24.912764340+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2023-07-03T19:01:24.913417048+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> emitting event: {"component_id":"main","capability_id":"contactSensor","attribute_id":"contact","state":{"value":"open"}}
2023-07-03T19:01:24.941536173+00:00 DEBUG Z-Wave Sensor  Garage Door - Left device thread event handled
2023-07-03T19:01:24.949701007+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2023-07-03T19:01:24.950271382+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> received Z-Wave command: {args={alarm_level=255, alarm_type=7, event="INTRUSION", event_parameter="", notification_status="ON", notification_type="HOME_SECURITY", v1_alarm_level=255, v1_alarm_type=7, z_wave_alarm_event="INTRUSION", z_wave_alarm_status="ON", z_wave_alarm_type="BURGLAR", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x07\xFF\x00\xFF\x07\x02\x00\x00", src_channel=0, version=3}
2023-07-03T19:01:24.960611882+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor -> v1 contact event
2023-07-03T19:01:24.961051465+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> emitting event: {"component_id":"main","capability_id":"contactSensor","attribute_id":"contact","state":{"value":"open"}}
2023-07-03T19:01:24.962050548+00:00 DEBUG Z-Wave Sensor  Garage Door - Left device thread event handled
2023-07-03T19:01:32.931725510+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2023-07-03T19:01:32.932359427+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> received Z-Wave command: {args={value=0}, cmd_class="BASIC", cmd_id="SET", dst_channels={}, encap="NONE", payload="\x00", src_channel=0, version=1}
2023-07-03T19:01:32.949930052+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor
2023-07-03T19:01:32.950368885+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> emitting event: {"component_id":"main","capability_id":"contactSensor","attribute_id":"contact","state":{"value":"closed"}}
2023-07-03T19:01:32.965207927+00:00 DEBUG Z-Wave Sensor  Garage Door - Left device thread event handled
2023-07-03T19:01:32.968308219+00:00 TRACE Z-Wave Sensor  Received event with handler unnamed
2023-07-03T19:01:32.968881510+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> received Z-Wave command: {args={alarm_level=0, alarm_type=7, event="INTRUSION", event_parameter="", notification_status="ON", notification_type="HOME_SECURITY", v1_alarm_level=0, v1_alarm_type=7, z_wave_alarm_event="INTRUSION", z_wave_alarm_status="ON", z_wave_alarm_type="BURGLAR", zensor_net_source_node_id=0}, cmd_class="NOTIFICATION", cmd_id="REPORT", dst_channels={}, encap="NONE", payload="\x07\x00\x00\xFF\x07\x02\x00\x00", src_channel=0, version=3}
2023-07-03T19:01:32.981245927+00:00 TRACE Z-Wave Sensor  Found ZwaveDispatcher handler in zwave_sensor -> v1 contact event
2023-07-03T19:01:32.981682010+00:00 INFO Z-Wave Sensor  <ZwaveDevice: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx [51] (Garage Door - Left)> emitting event: {"component_id":"main","capability_id":"contactSensor","attribute_id":"contact","state":{"value":"closed"}}
2023-07-03T19:01:32.986232177+00:00 DEBUG Z-Wave Sensor  Garage Door - Left device thread event handled

So does that not work properly with the stock Zwave Sensor driver? That looks like open was generated for open, close was generated for close, no?

I figured out the issue as to why this device is different. The stock Zwave Sensor driver has special code to handle the difference.

This device sends sensor updates using BASIC SET in a non standard way. Most devices use BASIC REPORT. So the stock driver has special logic for that:

The device ALSO sends “v1 style” notifications although its wrapped in a NOTIFICATION_V3 report. So the stock driver also has logic to handle that.

Yeah, oddly enough after rechecking today it looks like the stock driver may now be working OK, at least the open/close functionality. The app’s detail page for the device does show non-existent temperature placeholder, but thats fine. The history is showing the open/close events at the correct times. I know it wasn’t working the last couple of days, since some of my dependent intrusion detection automations based on them kept going off unexpectedly. Perhaps switching drivers a few times caused something to get reset in the device itself.

So effort on enhancing the “PH” driver may not be warranted for this device given a working driver exists. I report back if it breaks or stops working again in the near future.

1 Like

I don’t speak for Phil but I wouldn’t bother for a zwave (non plus) device that you can’t find even used. I had mentioned in another thread about how one of these Monoprice tilt sensors also had an external input and it also sent non standard messages for that as well. IMO its not worth it for an older and oddball device when newer, better, 100% supported devices are available (like the ecolink 2.5 or 5.0 tilt sensors).

2 Likes

So looking for some help with some monoprice/ecolink z wave PIR motion sensors. Was running these on a custom dth, but looks like they were migrated to edge yesterday and don’t seem to detect motion at all with the default edge driver.


Any chance you could add these to your driver channel. Can help in anyway. I have like 10 of these in my house and use them for all kind of automation.
Thanks.

Have you tried the “Z-Wave Sensor PH” Edge driver?

I installed “Z-Wave Sensor PH” driver from " Z-Wave Drivers - philh30" Channel and it seems to work fine. It shows an additional Illuminance capability which does not exist in Monoprice Motion Sensor 014F-2002-0203

Tried it still not working right. The motion never turns off. Seems to also think its an open/close sensor from the graphic

Did you just change drivers or did you exclude and re-pair the device? Sometimes you need to re-pair a it to work properly.

Just swapped the driver, I’ll try re pairing and see if that works.

Deleted one of the sensors and repaired still same issue.

Interesting that both @desiGeek and @userMT seem to have the same model (with fingerprint 014F-2002-0203) and one mostly works with Z-wave Sensor PH and the other does not. Note that the driver does not have this exact matching fingerprint currently, its only matching by device class at this point - thats why @desiGeek is seeing capabilities that don’t exist on the device and the more generic sensor presentation.

I’d be willing to add support for it to the driver but I’ll need more information/logs on it. A way to test would be ideal if I could get one used or borrow one.

To start off, what model Monoprice sensor is it? (its a 5 digit part number usually).

1 Like

Actually mine is Linear/GoControl branded GD00Z-4

Wapirz-1, they are rebranded go control, https://www.gocontrol.com/detail.php?productId=15
I can send you one if you want.

I’ll follow up via PM.

1 Like

In case this is of any help, there were two separate versions of the Gocontrol GD00Z4. The original was Z wave classic, the second one was zwave plus. The firmware was different, everything else was the same.

FAQ: Question about GoControl--Is it the same as Linear?

3 Likes

@csstup
If it’s possible, would you please add temperature and humidity offset options to the Z-Wave Sensor PH driver. The DTH had these settings and I really need them back because the Zooz 4-in-1 Sensor, model ZSE40, humidity measurements are ridiculously inaccurate.

1 Like

Anyone having issues with old " Monoprice Z-Wave Plus Door and Window Sensor, No Logo" sensors going offline, but still reporting open/close events? I’ve tried removing and re-adding using the default ST edge driver as well as this driver.

2 Likes

Same here. I think they don’t have anything like temp reporting, so unless it’s used often, it reports offline. I haven’t found a driver that won’t report it offline after a few hours.

1 Like

Updated notes in the original post. I’ve taken over support and additions to the original “Zwave Sensor PH” driver, moved it to my channel and renamed it Zwave Sensor CS.

Newly added is support for the WAPIRZ motion sensor from Linear, GoControl and Monoprice.

If you’re successfully using Zwave Sensor PH on your existing devices, you can continue to do so, nothing will change or break. You can migrate to Zwave Sensor CS if you’d like to.

Next up is supporting temperature/humidity offsets for all devices with those capabilities!

6 Likes