Inteset Motion/Light/Temp sensor

IT_Guy · February 4, 2023, 9:08pm

I found the INT-ZWAV-MTD Inteset Motion/Light/Temp sensor for under $16. Great price! You can find it if you use goo gle to search for it. But on amaz, for some reason you can't find it by searching. Looking at the reviews, one user posted that he was able to add it to his Hubitat. Unfortunately, he didn't elaborate on what built in device driver he used since for some reason there are no Inteset devices supported with built in drivers.

Well, I purchased four due to the great price!! Once received, I realized they must be a rebranded Dome product since they are the exact same size, design, etc to my 3 existing Dome motion sensors. However, my Dome sensors only provide motion and light (no temp).

Anyway..... after attempting several different drivers, the only one that I can get anything working on is the Dome motion sensor driver. However, even with this driver, I cannot get this device to do anything more than join, and report it's condition when it joins. After that its motion status stays on "active". When looking at the logs, I see communication stops with a 'warning' of "configure...".

The device state variables show are the same as the Dome (which I think is expected since that is the driver I chose), and many of the values are the same, but on different config values.

My working Dome device:
State Variables

configVal1 : 28
configVal2 : 30
configVal6 : 8
configVal7 : 180
configVal9 : 49
pendingRefresh : false
configVal10 : 0

My non working Inteset device:
State Variables

configVal1 : 28
configVal2 : 2
configVal6 : 30
configVal7 : 1
configVal9 : 49
pendingRefresh : true
configVal10 : 180

At any rate, I think the key is that the device log just keeps repeating "Config" whenever I wake the device up using the button on the device. Not much else in the logs.

dev:1952023-02-04 12:59:57.545 pm warn configure...
dev:1952023-02-04 12:20:58.897 pm warn configure...
dev:1952023-02-04 12:14:19.089 pm warn configure...
dev:1952023-02-04 12:13:06.411 pm infoZ-Wave command:SensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[0, 113], size:2, scaledSensorValue:113)
dev:1952023-02-04 12:10:52.402 pm infoZ-Wave command:WakeUpIntervalReport(nodeid:1, seconds:43200)
dev:1952023-02-04 12:10:52.366 pm infoZ-Wave command:WakeUpNotification()
dev:1952023-02-04 12:09:08.461 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 8, sequence: false, eventParametersLength: 0, eventParameter: [], sequenceNumber: 0)
dev:1952023-02-04 12:08:59.956 pm infoZ-Wave command:WakeUpNotification()
dev:1952023-02-04 12:08:57.484 pm infoZ-Wave command:WakeUpIntervalReport(nodeid:1, seconds:43200)
dev:1952023-02-04 12:08:57.377 pm infoZ-Wave command:SensorMultilevelReport(precision:0, scale:1, sensorType:3, sensorValue:[0, 22], size:2, scaledSensorValue:22)
dev:1952023-02-04 12:08:57.315 pm infoZ-Wave command:BatteryReport(batteryLevel:91)
dev:1952023-02-04 12:08:57.307 pm infoZ-Wave command:NotificationReport(v1AlarmType: 0, v1AlarmLevel: 0, notificationStatus: 255, notificationType: 7, event: 0, sequence: false, eventParametersLength: 1, eventParameter: [8], sequenceNumber: 0)
dev:1952023-02-04 12:08:34.494 pm infofingerprint mfr:"039A", prod:"0003", deviceId:"0106", inClusters:"0x5E,0x9F,0x55,0x86,0x73,0x85,0x8E,0x59,0x72,0x5A,0x80,0x84,0x30,0x71,0x31,0x70,0x6C"
dev:1952023-02-04 12:08:34.490 pm debugbuilding fingerprint for unknown Z-Wave device...
dev:1952023-02-04 12:08:32.459 pm debugconfigure() called...

I'm hopeful that someone with much more experience than I with this type of behavior might recognize it and be able to help me get these working. Thanks to anyone in advance!!

IT_Guy · February 5, 2023, 6:43pm

An update:
I'm fairly new to Hubitat and the community. If this is the wrong place to post this kind of thing, let me know.

I tried a couple dozen of the built in drivers and found that the Fibario Motion Sensor driver does correctly get light and motion values correctly from the device. In addition, the Fibario device is clearly based on the same device design etc. The Fibario driver driver doesn't correctly get the temp data though. I can limp along with this, but sure would be nice to be able to get temp data as well as be able change the existing configuration of the device.

Also trying to manipulate the settings for the device via the Fibario driver can't really be used since it seems that the settings in that driver map to different parameters on the Inteset device.

After doing a factory reset on the device, I then re-added the device via the Hubitat "Add Device" process. In that process I chose the Fibario device driver. Then gave the device a name... next... Then was shown the device information page. I did notice though that at this point the "device type" drop down was just set to "Device". I had to click the drop down and choose the Fibario Driver again:

State Variables eventually popuplate with:

wakeUpInterval : 43200
configVal1 : 3
configVal2 : 2
refreshAll : false
configVal6 : 30
lastBattery : 1675562695
configVal8 : 0
configVal9 : 100
pendingRefresh : false

Current States

battery : 83
illuminance : 164
motion : active
pendingChanges : 19
threeAxis : [x:0,y:0,z:0]

The documentation that comes with the device does list the parameters as follows:
#1 Motion Sensitivity Level
Available levels are 8 - 255

#2 On/Off Duration for Motion staying active
Available settings are 5-600 (seconds)

#3 Basic Set Level. (I don't really get what this setting is, so I'll just state what the instructions say...) Basic set command will be sent where contains a value when motion sensor is triggered, zwave gateway will take it for consideration. For instance if a lamp module is received the Basic Set command of which value is decisive as to how bright or dim level of the lamp module shall be. This parameter is used to some associated devices.
Available settings are 0 or 1-99 or 255.0 - OFF. Alarm cancelling or turning a device off, 1-99 or 255 - ON. (Binary switch device;Dim Level (Multilevel Switch Device Default setting: 255.

#4 PIR Detecting Enabled/Disabled
Available settings: 0 or 255.0
Default is 255 (ON)

#5 Ambient Light Level
Parameter size 2 byte
Available settings 0-1000

#6 PIR Re-Trigger interval setting
Available settings 1-8 (seconds)

#7 Light sensor polling interval
Parameter size 2 byte
Available 60-36000 (seconds)

#8 Lux Level Function Enable/Disable
Parameter size 1 byte
Available 0 or 1 (Manual says 0 is Enabled. But I wonder if it's actually 1 since the Lux sensor is on out of the box)

#9 Ambient Illumination Lux Level Differential Report
Parameter size 1 byte
Available 0 - 100 (Lux)

#10 Ambient Temperature Differential Report
Parameter size 1 byte
Available 0 - 127

#11 Led Blink Enable/Disable
Parameter size 1 byte
Available 0 or 1 (Default 1, ON)

#12 Motion Event Report One Time Enable
Parameter size 1 byte
Available 0 or 1 (Default is 1)

#99 Ambient light intensity calibration
Parameter size 2 byte
Available 1-65536
Default is 1000

njanda · February 5, 2023, 8:52pm

You could see if the 3 in 1 Zwave drivers HERE
report all the attributes you’re after.

IT_Guy · February 5, 2023, 10:00pm

Thanks for the idea. Unfortunately now all I get is Battery level info. Here are the logs after changing to the new imported driver. Tried using the Refresh, Poll, and Configure buttons. Waited a few minutes between each.

dev:1962023-02-05 01:58:04.894 pm errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_royski_Devolo_Contact_Sensor_609.refresh() is applicable for argument types: () values: []
Possible solutions: every(), parse(java.lang.String), every(groovy.lang.Closure), grep() (method refresh)
dev:1962023-02-05 01:57:21.552 pm debugparse() >> description: zw device: 17, command: 3105, payload: 03 0A 00 15 , isMulticast: false
dev:1962023-02-05 01:57:01.612 pm infosending commands: [ConfigurationSet(parameterNumber: 3, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), ConfigurationSet(parameterNumber: 4, defaultValue: false, size: 1, configurationValue: [99], scaledConfigurationValue: 99), ConfigurationSet(parameterNumber: 5, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), ConfigurationSet(parameterNumber: 6, defaultValue: false, size: 1, configurationValue: [4], scaledConfigurationValue: 4), ConfigurationSet(parameterNumber: 7, defaultValue: false, size: 1, configurationValue: [54], scaledConfigurationValue: 54), ConfigurationSet(parameterNumber: 8, defaultValue: false, size: 1, configurationValue: [3], scaledConfigurationValue: 3), ConfigurationSet(parameterNumber: 9, defaultValue: false, size: 1, configurationValue: [4], scaledConfigurationValue: 4), ConfigurationSet(parameterNumber: 10, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 11, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 12, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 13, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 20, defaultValue: false, size: 1, configurationValue: [30], scaledConfigurationValue: 30), ConfigurationSet(parameterNumber: 21, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), ConfigurationSet(parameterNumber: 22, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), WakeUpIntervalSet(nodeid:1, seconds:86400), BatteryGet(), SensorBinaryGet(sensorType:10), SensorBinaryGet(sensorType:12), SensorMultilevelGet(sensorType:1, scale:0), SensorMultilevelGet(sensorType:3, scale:0)]
dev:1962023-02-05 01:56:39.366 pm errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_royski_Devolo_Contact_Sensor_609.poll() is applicable for argument types: () values: []
Possible solutions: wait(), run(), run(), any(), grep(), dump() (method poll)
dev:1962023-02-05 01:54:53.675 pm debugparse() >> description: zw device: 17, command: 7105, payload: 00 00 00 FF 07 00 01 08 , isMulticast: false
dev:1962023-02-05 01:54:12.838 pm debugparse() >> description: zw device: 17, command: 3105, payload: 03 0A 00 A2 , isMulticast: false
dev:1962023-02-05 01:54:11.843 pm debugDevolo Motion Detected
dev:1962023-02-05 01:54:11.836 pm infoDevolo cmd.sensorValue: 255
dev:1962023-02-05 01:54:11.807 pm debugparse() >> description: zw device: 17, command: 3003, payload: FF 0C , isMulticast: false
dev:1962023-02-05 01:54:11.585 pm infoDevolo: BatteryReport BatteryReport(batteryLevel:83)}
dev:1962023-02-05 01:54:11.582 pm debugparse() >> description: zw device: 17, command: 8003, payload: 53 , isMulticast: false
dev:1962023-02-05 01:54:08.644 pm infoDevolo: BatteryReport BatteryReport(batteryLevel:83)}
dev:1962023-02-05 01:54:08.618 pm debugparse() >> description: zw device: 17, command: 8003, payload: 53 , isMulticast: false
dev:1962023-02-05 01:54:08.221 pm infosending commands: [ConfigurationSet(parameterNumber: 3, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), ConfigurationSet(parameterNumber: 4, defaultValue: false, size: 1, configurationValue: [99], scaledConfigurationValue: 99), ConfigurationSet(parameterNumber: 5, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), ConfigurationSet(parameterNumber: 6, defaultValue: false, size: 1, configurationValue: [4], scaledConfigurationValue: 4), ConfigurationSet(parameterNumber: 7, defaultValue: false, size: 1, configurationValue: [54], scaledConfigurationValue: 54), ConfigurationSet(parameterNumber: 8, defaultValue: false, size: 1, configurationValue: [3], scaledConfigurationValue: 3), ConfigurationSet(parameterNumber: 9, defaultValue: false, size: 1, configurationValue: [4], scaledConfigurationValue: 4), ConfigurationSet(parameterNumber: 10, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 11, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 12, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 13, defaultValue: false, size: 1, configurationValue: [12], scaledConfigurationValue: 12), ConfigurationSet(parameterNumber: 20, defaultValue: false, size: 1, configurationValue: [30], scaledConfigurationValue: 30), ConfigurationSet(parameterNumber: 21, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), ConfigurationSet(parameterNumber: 22, defaultValue: false, size: 1, configurationValue: [0], scaledConfigurationValue: 0), WakeUpIntervalSet(nodeid:1, seconds:86400), BatteryGet(), SensorBinaryGet(sensorType:10), SensorBinaryGet(sensorType:12), SensorMultilevelGet(sensorType:1, scale:0), SensorMultilevelGet(sensorType:3, scale:0)]
dev:1962023-02-05 01:54:07.977 pm debugparse() >> description: zw device: 17, command: 8407, payload: , isMulticast: false
dev:1962023-02-05 01:53:59.069 pm debugparse() >> description: zw device: 17, command: 7105, payload: 00 00 00 FF 07 08 00 , isMulticast: false
dev:1962023-02-05 01:53:54.483 pm errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_royski_Devolo_Contact_Sensor_609.refresh() is applicable for argument types: () values: []
Possible solutions: every(), parse(java.lang.String), every(groovy.lang.Closure), grep() (method refresh)
dev:1962023-02-05 01:53:25.321 pm debugparse() >> description: zw device: 17, command: 7105, payload: 00 00 00 FF 07 00 01 08 , isMulticast: false
dev:1962023-02-05 01:52:54.688 pm debugparse() >> description: zw device: 17, command: 3105, payload: 03 0A 00 C6 , isMulticast: false
dev:1962023-02-05 01:52:54.651 pm debugparse() >> description: zw device: 17, command: 7105, payload: 00 00 00 FF 07 08 00 , isMulticast: false
dev:1962023-02-05 01:51:42.685 pm errororg.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: user_driver_royski_Devolo_Contact_Sensor_609.refresh() is applicable for argument types: () values: []
Possible solutions: every(), parse(java.lang.String), every(groovy.lang.Closure), grep() (method refresh)

IT_Guy · February 5, 2023, 10:29pm

FYI.... When I changed the driver back to the Fibario Motion Sensor driver the device became unresponsive with regard to Motion and Illumination. I had to remove the device, perform a factory reset on the device, then re-add the device. Even then the device only started working again after a several minutes.

Just posting in case anyone else runs into similar behavior.

JJJS · February 7, 2023, 4:27pm

Switch to the default "device" driver and click "delete states", then switch it to "Neo Motion Sensor 700".

That's the driver currently working best for me. Reports incredible lux accuracy and motion. Unfortunately haven't gotten temperature readings to work yet. Will update if so. Definitely worth it for the price imo!

IT_Guy · February 9, 2023, 12:53am

Hmmmm. There is no way to switch back to the "Default" driver.

Are you suggesting to do that because I will gain configuration control of some kind?

IT_Guy · February 9, 2023, 6:23pm

Unfortunately, now the battery is draining very fast. Not sure if that could be related to the driver. The only thing that has changed is I have physically installed it. From the time it was installed to now, the battery has gone down from 79 to 58. It's only been 16.5 hours. The only things in the logs are related to illumination updates. No motion there in that time.

Could that be because of the incorrect driver? Or is this normal for a sensor which reports LUX?

IT_Guy · February 10, 2023, 12:29am

I removed the device from Hubitat. Factory reset the device. Added it back in as Neo Motion Sensor 700. I only really started working after about 20 minutes. But even then, only correctly reporting motion and Lux. Now I don't get battery info so I'll have no idea how quickly it is draining.

@JJJS
Is this what yours is showing as well?

Also, the State is only showing two items now:

reconfigure : true
configUpdated : true

BTW, I had sent an email to Inteset regarding Hubitat drivers. Their response pointed me to what I believe is your post on their forum from a couple of days ago. They also let me know that this device is being discontinued.

mwh · May 15, 2023, 6:59pm

I was tempted by the price on Amazon and bought a couple of these to experiment with. This model definitely does not have the temperature capability the product page implies or the included paper doc describes. I confirmed this by pulling command class and parameter reports from a sensor fresh out of the box.

I got tired of using the Basic Z-Wave Tool to configure them and modified a Homeseer motion sensor driver to work with the Inteset. It receives motion, illuminance and battery reports, and will update the configuration params whenever the device wakes up (with the button or at the preset interval).

https://raw.githubusercontent.com/mwhdc/hubitat/main/inteset-zwave-motion-sensor.groovy

system · May 14, 2024, 7:00pm

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