Similar, not identical. For example, physicalgraph is not a namespace that exists in Hubitat. Often, the replacement is com.hubitat, but you can find more information on porting code if you search. I really did mean it when I said that some of this won't work on Hubitat.
Again, What I said above is true. Specifying runLocally does nothing if you're not a SmartThings engineer (I don't even think it lets you, so that would explain the error...apparently you're on SmartThings? That would be good to state because it's not an assumption I'd make if you were posting in this thread), and it is not necessary on Hubitat because everything runs locally anyway.
No, mine is instant because it runs locally, and it's one of the reasons I left SmartThings.
No, the IDE just didn't throw an error when you set that value. I repeat: it does nothing, not unless you are an ST engineer baking specific SmartApps or DTHs into the ST hub firmware, the only way anything runs locally. This article explains more: https://support.smartthings.com/hc/en-us/articles/209979766-Local-processing#What (and a device running locally really doesn't matter when the majority of SmartAppps that allow you to actually use them don't run locally).
If local execution is important to you, I think Hubitat is a great choice. It's similar enough to SmartThings that if you've been using ST for a while, you're likely to get the hang of it quickly--and there are always a bunch of helpful people here if you get stuck!
Hello I'm very new to hubitat.
I bought the hub and I was thinking about a motion sensor.
I found Konke and I bought almost everything, the hub, the ir controlle, a couple of motion sensor and a contact switch for doors and windows.
I tried the konke hub but It hasn't configuration options.
SO my question is how can I configure all of them in hubitat hub??
I change my question, I menage to discover the sensor but I don't see any event.
How to set the door switch?
The Konke hub does not integrate with Hubitat. (I'm not sure if that's what you were trying to do or just something you tried initially and now want to see if you can use these devices elsewhere instead.) If you want devices that work with Hubitat with a minimum of hassle, I'd recommend sticking to the list of compatible devices: https://docs.hubitat.com/index.php?title=List_of_Compatible_Devices.
That being said, far more devices than are on this list will work with Hubitat. This includes most Z-Wave and Zigbee devices. It's still a good idea to check the list or the forums. For example, the Konke motion sensor is not officially compatible (not on that list) and can be made to somewhat work but doesn't seem to be able to be configured correctly to work well as far as anyone using Hubitat has been able to do (only been able to get it to report motion "active" events, so not really useful). I did have luck with the Konke temperature/humidity sensor, though no built-in driver exactly matches its capabilities.
I don't know about the door or window sensors. If any driver would work, it would be the "Generic Zigbee Contact Sensor" driver. Try resetting the device and pairing it to Hubitat via regular Zigbee discovery (you'll have to consult the Konke documentation to see how to reset it or put it in pairing mode). Change to this driver, click Save, and be sure to hit "Configure" after you switch to the new driver. This might not work but is your best hope.
tl;dr nobody knows about most of these because most people haven't tried most of these devices. At least one works well, and another pairs but doesn't really work fully. Your luck may vary with other devices.
Had some extra time last night so I thought I'd pull this one out of the junk bin. Since converting my C-4 test hub to a second production hub, I've got a place for the problem children to live. Set the Zigbee channel to 20 and the Konke motion sensor joined right away. Loaded up your driver and after a few minutes (don't know why that initial delay) the motion sensor started working. I've been testing it every so often over the last 24 hours and it's not failed yet.
Thanks for this! Nice to have another motion sensor available, even if its field of view is very narrow. Might find a particularly good use for those characteristics. What have you used yours for, or are you using it at all?
I "liked" it so much that I'm using it outside, "protected" by clear packing tape in most directions (just wrapped some around the perimeter and made a little overhang on top). It's hung underneath a rail on my wooden fence but otherwise probably fairly exposed to the elements (rain, snow, cold, sun, etc.). So far, it's survived.
Because it's pretty much useless for motion in most cases, this is (obviously) something I'm using outdoors, and my use case is simple: detect when I'm walking towards my backdoor from my backyard (often if I just drove and parked my car there). I use this as part of an outdoor lighting automation, and since I don't care to keep the light on if motion is continuously active (something not really likely to happen here, anyway), I don't care that I have no idea when activity stops--which, as you know, the driver just takes a stab at.
It's a manufacturer specific cluster...
Unless you sniff the frames while this device is connected to it's native hub while monitoring what it produces via its native app, it's unlikely you will be able to decode these payloads.
Now having said all that, encoding 42 is an ascii string, which may be readable and easier to decode...
I've been able to pair my Konke motion sensor (which has the same device footprint) with your driver but for some reason it doesn't display or detect motion under the device attributes. Any ideas?
And I can confirm it works on Channel 15 but it didn't work on channel 24. I'm SmartThings user so I can't say anything about compatibility with Hubitat though.
