Alwas’ problem sounds reminiscent of my problem with the OOMI Multisensors. OOMI Support helped me fix it. We couldn’t figure out where in your DH to insert this line:
//Disable Parameter setting Lock
zwave.configurationV1.configurationSet(parameterNumber: 0xFC, size: 1, scaledConfigurationValue: 0),
so we inserted it into the Vandervoort DH, applied it to the device and now I can use your DH or the stock SmartThings Aeotec Multisensor 6 DH to control the OOMI Multisensor. If you could add that line into your code or suggest to me where to insert it, I could test it with an unconfigured OOMI Multisensor. Once successful, you could boast additional device functionality for your DH.
@erocm1231 great DTH! Is there a way to have different reporting interval for the different parameters (temperature, humidity,etc). I’m using the temperature element as a remote sensor for my AC, and need the fast update (30s) but could use a different interval for the other element so not too jam the log. Thx.
Thank you for the work on this! I started out on the ‘official’ one, but the reporting want working for me, so after poking around and discovering yours, It’s Is working for me on V1.08. Motion didn’t work at first but I suspects it had to time out of the old period before the new setting would take effect.
Truth be told though, I’m a bit saddened that its taking Aeon almost a year to finalize v1.09…
@lolo I was looking through the documentation while troubleshooting my motion not working. This isn’t an option due to the device limitations. It might could be implemented into the DTH, but the device would still be sending it behind the scenes.
To keep the log from jamming, could you set the interval to 1 minute? A 30 seconds shouldn’t make much of difference on a houses a/c system.
I certainly could setup the log to 1 min for this application, but I was hoping to report the parameters I don’t need only once every few hours…
I recently purchased a couple of these and found Eric’s DTH to be GREAT. However, I am not a big fan of ‘click to reset’ on the interface so I optimized the interface and added/fixed a few items to my personal taste, including adding an area to put in the date of replacement. Kudos to @erocm1231 and I offer this as an expansion of his efforts.
@CodyO What? There is a version 1.09? I though the 1.08 was still in beta…
You need to contact Aeon Labs Support to attain it.
that is how i received a copy
I’ve been trying this device handler with my OOMI sensor as well, still haven’t figured out where to change the parameter based around Aeon’s suggestion, is it inside the device handler??
"Everything about the Oomi Multisensor is more or less the same as the Multisensor 6 in this case. There is one option that is enabled in Oomi version that locks its configuration in place, but can be easily disabled. (All internal settings are pretty much the same).
Oomi version has its default set to 1, so to unlock everything you can set Parameter 252 [1 byte] = 0 which will allow you to configure the Oomi Multisensor just like our Multisensor 6 product."
What are the updates in 1.09? I’m actually still running 1.07.
The only thing i know about is the reduction of the LED firing off every time it sent info.
As of today there is no official releases for 1.09 so no updates docs either.
Struggling a tiny bit with this one. I have a multi sensor installed outside, and as expected, the motion detector is useless. So I have tried to disable it (by entering 0 for sensitivity), but I still see “Motion detected” in the recently tab every minute or so…
Is there constant movement? The two I just got work great…one’s vibration sensor goes off when the wind blows, but the motion sensor is stable.
The boiler’s flue is in the field of view, which explains the constant movement
BUT sensitivity has been set to 0 which should disable the motion sensor altogether.
No idea of why it is still detecting motion every 2/5 mins…
Firmware versions 1.10 for US/AU and 1.11 for EU were posted yesterday. 1.08 was removed. I haven’t yet tested 1.10.
Here is the change log:
V1.10 + V1.11:
Added addition setting for Parameter 81 to completely disable LED.
Parameter 81 [1 byte size]
0 = All LED allowed
1 = Disable Motion sensor only.
2 = Disable all LED activity
Size change for Parameters 41, 49, and 50 to 4 byte size.
Updated Z-Wave Library
US, AU frequency V1.10 equivalent to V1.11 EU frequency.
Version CC and Manufacturing CC listed under secure network.
Improved accuracy of lighting sensor
I’m assuming we’ll have to wait until the DTH is updated correct?
I believe we’ll have to wait until the DTH is updated.
I have used the Z-wave tweeker to manually set the Parameter 81 to “2” and i still have the LED coming on.
It might be getting overwritten by the device handler’s own options for this field 0 or 1.
Awesome, I’m glad they are still working on this sensor as it is a great device. I’ll update the parameters.
Also, can you post the RAW Description from the IDE for the OOMI sensor?
I don’t know if anyone can help, but I updated the Multisensor to 1.1 and pushed the latest version of erocm1231’s code to my hub.
But one of my two Multisensors doesn’t seem to respect the “LED Off” command, as the LED continues to blink at me every so often. Do I need to “flush” the Hub or do anything on my end to make sure everything works as it should?
Also there’s a orange dot next to the “Configure” tile in the settings for Multisensor, does that mean anyting bad?
@erocm1231, the Raw Description for one of my OOMI sensors is:
zw:Ls type:2101 mfr:0000 prod:0000 model:0000 ver:0.00 zwv:0.00 lib:00 cc:5E,86,72,59,85,73,71,84,80,30,31,70,98,7A,5A
for the other, it’s:
zw:L type:2101 mfr:016A prod:0102 model:0064 ver:1.04 zwv:4.05 lib:03 cc:5E,86,72,59,85,73,71,84,80,30,31,70,7A,5A role:06 ff:8C07 ui:8C07