I’m wanting to change the motion sensitivity to “2” and I do not understand where to do this? Any help would be appreciated.
1 Like
What’s the difference between this device handler and one linked on @TheSmartestHouse site?
This was written ground up and tweaked to meet the needs of this brand/sensor. So couple of things were addressed in this version:
- New UI interface to make it easier to use
- The pairing and configuration process has been optimized for ZooZ. There were design issues in the old handler which was based off some GitHub sample code which had an inherent issue in it
- Some new additional features like polling etc
It’s just a more comprehensive alternative version developed based on user request which addresses some issues pointed out above. See the first post for more details:
1 Like
Sure, just click on the gear icon and it’ll open up the preferences page where it has detailed explanations for each setting. You can set the motion sensitivity there.
Thank you. I’ll give it a try.
1 Like
Configure tile doesn’t do anything. Also after hitting gear icon I can’t read the full descriptions for the settings. They are cut off. Would be nice to have a post here with the settings and what they do. The very last setting for me has no description at all.
You’re probably posting on the wrong thread. There is no configure button in this device handler. It’s all automatic. This is what this handler looks like:
Just me being an idiot and having the wrong device handler installed! Sorry and THANKS!
Ok, correct device handler now…no icons however.
1 Like
I’m guessing you’re using an Android phone. That’s a bug with the ST Android apps. This has been reported to @slagle and @Jim to pass onto the Android product dev team. I’ve been told that it’ll be fixed in the next ST Android app release. @slagle can you please confirm.
Great, thanks!
1 Like
Just connected one of these up and it works for the most part. I cannot get it to take any of the settings, specifically motion which I want set to 1 minute.
I see this in the log:
c2e8e9b2-7d96-4426-8905-a7ca0719a34b 11:37:39 PM: debug Requested a refresh of sensors and settings at next wakeup
c2e8e9b2-7d96-4426-8905-a7ca0719a34b 11:37:39 PM: trace Update called settings: [noMotionTimeout:1]
But motion is still 3 minutes.
Looking at the code seems I should see “Device woke up” in the logs when the device wakes up and is ready to be configured. That has not happened yet, nor does it happen if I press the button as instructed.
As I said, all functions are working, I just cannot get it to take the settings.
Any thoughts?
Have you tried the instructions in the first post to force initialize the
settings for the device?
As for wake up it depends upon the configured interval. By default it’s
3600 seconds. It will take the settings either when it wakes up next or
when you force it using the instructions in the first post
“This was written ground up and tweaked to meet the needs of this brand/sensor.”
So was my code. MANY HOURS were spent writing exception handling for a notification command set that sends
inconsistent information.
- New UI interface to make it easier to use
In your opinion. There’s nothing “new” (or easier) about the tile layout style. I offer two different layouts, would posit that icons are worthless, and, my configuration parameters work, sans workarounds.
“2. The pairing and configuration process has been optimized for ZooZ. There were design issues in the old handler which was based off some GitHub sample code which had an inherent issue in it”
This sounds like it was written by my marketing folks. Because you put fingerprints in it for v1 and v2 hubs? I don’t own a v2 so, well I don’t care to put a v2 fingerprint in it. Also, “based off some GitHub sample code” and “inherent issues”? Please, do elaborate. There’s nothing at all special to the zooZ product line with the way it pairs, or the way it is configured. It is a Z-Wave certified device which means it MUST operate per the Z-Wave specifications set forth in the standard. This is what makes Z-Wave great. In fact you can go on Z-Wave alliance’s website and get the engineering spec for it.
- Some new additional features like polling etc
There’s nothing new here. Polling? You can’t “poll” a battery powered device. You can ADD a poll feature but because they are sleeping devices, you can only request things when they wake, which, you do state, so really, this point is moot and just sounds good. So I have a device that sends reports when the state of the environment changes, when motion occurs, why, would I want to know an updated status of everything every four hours or even right away when the values sent are already current? In the hopes PERHAPS the temperature shifted a tenth of a degree or the humidity increased by the same?
“It’s just a more comprehensive alternative version developed based on user request which addresses some issues pointed out above. See the first post for more details:”
You really haven’t pointed out anything other than ease of pairing, which is really not hard. If you have to get into an IDE to load a device type, switching a sensor over to the other type is hardly an effort.
If you can’t tell, I take your comments as a bit more than a slight against my efforts, which, if anyone cares were available in v 1.2 , so several iterations of code, about 40 days prior to your device type. My code, I will freely point out was evolution of existing device types from SmartThings developers themselves like Duncan, and actually spun off from my Aeon Labs Mutisensor 6 code which goes way back now, and many others inputs in the community. I’m sure you just developed in a vacuum without help or guidance from anyone, using not one line of “sample code” from anywhere, certainly never used my code as a reference, to provide the miracle you have here.
I’m sure I could come across less irritated, but that’s ok because I am. It doesn’t bother me that you want to be super gung ho about this and act like a rockstar saviour of all of us home automatons. It does irk me a little that you’re monetizing this open source / open forum and shutting access to code down to those willing to pay the price. I think that goes against the community and the spirit of open source. Though you call it “donations” that is like “campaign contributions” of hundreds of thousands of dollars from banks to a presidential nominee… Most of all, I do not appreciate you pissing on my efforts 40 days late.
And lastly, I only found out about this because you were mentioned to me by my contact at Lorenz HD (makers of zooZ) who was considering using you as their “official” source of software and support. Despite this ^^^ I told them I completely understand, I’m a part time ST coder, have a day job and a family, and so long as you could provide quality software and responsive support, more power to them. So, all of this aside (I’m pretty over it already), I just hope you and your team, will provide well for them. I think Lorenz / zooZ has great potential in the emerging “consumer grade HA” world.
Sorry forum. I hate to have had to bring any drama in here outside of that which ensues with platform and firmware updates. I just couldn’t let this one slide. I’ve spent too many nights awake working on this stuff to let it slide without a word.
6 Likes
Hey @Robert_Vandervoort, no worries. I used your code and it’s great. Thanks for your efforts and hope to see more.
3 Likes
###Enhanced ZooZ 4 in 1 Sensor (ZSE40) Device Type - Version 2.1.0
- Added support to report code version and name to check for automatic updates
I just installed the handler and for illuminance, it reports value in %, but how can I tell the lumens so I can fine tune it with smart lighting to only turn on at certain illuminance level. If the device shows 50%, how can i tell the lumens to type into the smart lighting illuminance value.
Unfortunately it only reports a % change from the device. Maybe @TheSmartestHouse can comment on the range of lumens for the % mapping.
Thanks for calling is out @RBoy. We’re checking for a map of % to LUX with out engineers and will post the reply as soon as they come back to us.
look forward to hearing back your findings.
