Orvibo Motion sensor need help with driver

🛎️ Get Help
1

Hi guys, Friend using ST and wanted to move to Hubitat but he got tons of Orvibo motion sensors and I couldn't get it to work trying to port a DTH from ST over.
The DTH is this

I couldn't get motion to go active but here's the log when it's detecting motion.

dev:14942018-08-26 13:46:39.353:errorgroovy.lang.MissingMethodException: No signature of method: com.hubitat.zigbee.Zigbee.isZoneType19() is applicable for argument types: (java.lang.String) values: [enroll request endpoint 0x01 : data 0x002D] on line 68 (parse)
dev:14942018-08-26 13:46:39.326:debugParsing: enroll request endpoint 0x01 : data 0x002D

Line 68 is this

68 if (zigbee.isZoneType19(description)) {
69 name = "motion"
70 def isActive = zigbee.translateStatusZoneType19(description)71
71
72 value = isActive ? "active" : "inactive"
73 descriptionText = getDescriptionText(isActive)
74 } else if(description?.startsWith("read attr -"))
75 map = parseReportAttributeMessage(description)

any help would greatly appreciated. Tried a bunch of other drivers with no success.

2

There's nothing special about this motion sensor (aside from not reporting inactive on its own), did you try any of the built in drivers?
And if so which ones?

3

I tried these drivers

Generic zigbee motion

dev:14942018-08-26 17:37:46.265:debugparse: listResult [[name:motion, value:active, descriptionText: Orvibo motion is active]]
dev:14942018-08-26 17:37:46.262:debugparseIasMessage: resultListMap [[name:motion, value:active, descriptionText: Orvibo motion is active]]
dev:14942018-08-26 17:37:46.261:info Orvibo motion is active
dev:14942018-08-26 17:37:46.260:debugparse: zone status 0x0001 -- extended status 0x00

NYCE Motion sensor series

dev:14942018-08-26 18:01:34.737:debugparse: listResult [[name:motion, value:inactive, descriptionText: Orvibo motion is inactive]]
dev:14942018-08-26 18:01:34.736:debugparseIasMessage: resultListMap [[name:motion, value:inactive, descriptionText: Orvibo motion is inactive]]
dev:14942018-08-26 18:01:34.735:info Orvibo motion is inactive
dev:14942018-08-26 18:01:34.733:debugparse: zone status 0x0001 -- extended status 0x00

Bosch Motion detector

dev:14942018-08-26 18:06:17.391:info Orvibo motion is active
dev:14942018-08-26 18:06:17.386:info Orvibo motion tamper is clear
dev:14942018-08-26 18:06:17.380:debugzone status: alarm1Set:true, alarm1: 1, tamperSet: false, tamper: 0
dev:14942018-08-26 18:06:17.377:debugraw: zone status 0x0001 -- extended status 0x00

and you are right about no inactive report but how do I modify your driver with this ?

if (value == "active") runIn(120, stopMotion)

Then create a method called stopMotion:

> def stopMotion() {
>    sendEvent(name:"motion", value:"inactive")
> }
4

Most zigbee motion sensors have a timeout in the range of 15 to 30 seconds, if you're ok with 15 seconds, I can add the fingerprint for the orbvio along with the code required to the generic zigbee motion sensor driver.
We do not publish all our driver code, there are a few examples we have posted in our public github repo however.

5

That would be perfect. here's the Raw Description

01 0104 0402 01 05 0000 0003 0500 FFFF 0001 05 0000 0004 0003 0005 0001

6

Do you have the complete fingerprint when it paired to HE?, its located by clicking more while the device is pairing,

7

Manufacturer: ORVIBO Product Name: Device Model Number: 895a2d80097f4ae2b2d40500d5e03dcc deviceTypeId: 12
more...

manufacturer:ORVIBO
address64bit:00158D0001C1237D
address16bit:2BAA
model:895a2d80097f4ae2b2d40500d5e03dcc
basicAttributesInitialized:true
application:02
endpoints.01.manufacturer:ORVIBO
endpoints.01.idAsInt:1
endpoints.01.inClusters:0000,0003,0500,FFFF,0001
endpoints.01.endpointId:01
endpoints.01.profileId:0104
endpoints.01.application:02
endpoints.01.outClusters:0000,0004,0003,0005,0001
endpoints.01.initialized:true
endpoints.01.model:895a2d80097f4ae2b2d40500d5e03dcc
endpoints.01.stage:4

1 Like
8

I'm a little confused, does the hubitat need the device handler above to discover the orvibo motion sensor?
I used the above device handler on smartthings and it worked.

But I can't get hubitat to discover the orvibo motion sensor with or without the device handler code installed in drivers code.

Am I doing something wrong?

9

You don't need the driver above to discover the motion sensor. It's working with the generic Zigbee motion driver.
Try bringing the sensor closer to the Hub for discovery. Reset the sensor first by holding the button until the light start blinking.

10

Thank you for responding.
I've tried that. Tried turning off smartthings hub and hue hub so only the only zigbee network was hubitat.
Sensor is within 1 metre of hubitat hub.
Tried resetting by press and hold button until light was flashing faster. Nothing is reported by hubitat during discovery.
Thanks again for clarifying the driver is not required.

11

I understand you're new to the Community... welcome.

You can find a thousand stories of difficulties people have had with pairing devices. Zigbee, ZWave, Hue, even Lutron. I've read them all, it's not fun reading because the frustration level is never fun to observe.

The number one thing is, a device must NOT believe it belongs to another network. If it has ever been paired with a controller, anywhere in the world, including the factory, it needs to be Excluded first. It needs to be told to abandon the network number it thinks it's joined. Zigbee and ZWave have completely different Exclude procedures.

Clearly the first thing I "hear" when reading about pairing problems is.. it's not excluded yet. If you're sure that the device is ready to pair, then the next problem could be your Zigbee mesh. Again, you'll find those stories here too. There are certain Zigbee devices that do a really bad job of routing messages, but they also seem to be very quick to capture the traffic. They don't forward it properly or mangle it first. Even if the Hub is the closest physical device, some other Zigbee device COULD be forwarding the traffic, and mangling it. People have reported that turning off X fixed it for them, allowing the device to really really talk to the hub.

Once you get it to pair, it might not find a driver automagically. The hub might pick a generic driver or no driver at all (called "device.") This is where you need to consider the driver code up above.

2 Likes
12

Another common problem has been the Hub’s Zigbee channel. What is your hub’s Zigbee channel? Most have found channels 19-21 to be the most compatible with the widest array of devices.

1 Like
13

I have my Hubitat zigbee channel on channel 20. According to the Orvibo manual. the channel for this sensor should be 11,14,19,20,24,25.
don't forget to check your device list. Maybe it's there with name such as "device" or "generic zigbee motion sensor"
I went and look at my ST hub for curiosity and it's also on channel 20. I am screwed since I can't change my ST zigbee channel and too many devices to deal with on Hubitat to change channel. Crossing my finger for interference.

14

I've bought one of these recently and the timeout doesn't seem to work. The fingerprint is different though. Any chance of getting the latest model added with the built-in 15 second time-out?

Fingerprint:

ID: F56E
Manufacturer: 欧瑞
Product Name:
Model Number: 585fdfb8c2304119a2432e9845cf2623
deviceTypeId: 15
manufacturer : 欧瑞
idAsInt : 1
inClusters : 0000,0001,0003,0500
endpointId : 01
profileId : 0104
application : 202020202020202020202020203832313135312E32312E3176
outClusters : 0003
initialized : true
model : 585fdfb8c2304119a2432e9845cf2623
stage : 4

15

Im confused, what timeout are you talking about, motion inactive?
With very few exceptions the device is responsible for sending motion inactive.

16

These are one of the very few exceptions as per your post in this thread: "There's nothing special about this motion sensor (aside from not reporting inactive on its own)..."

17

Oic, yeah remembering now, the generic zigbee motion sensor has a special case when the manufacturer is ORVIBO, it then runs a motion inactive 15 seconds later. Since the manufacturer of this device is obviously not ORVIBO this isn't working, I'll see what I can do.

1 Like
18

Cheers @mike.maxwell I appreciate it. I thought I was going mad until I found that comment of yours about them not sending an inactive message.

19

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.