So this is confusing (as usual about Hubitat for me). I thought I installed Kkossev driver, Package manager reports this:
But when I go to hub's Drivers code, it sais name spaces Gassgs:
But when I go to hub's Drivers code, it sais name spaces Gassgs:
Yeah, that's gassgs's fork. Which works fine for many users, but I don't recall if it displays the firmware version.
I use Krassimir's mmW driver since it enables the setMotion-Inactive command (which I find useful for troubleshooting).
1 Like
The confusion continues. The driver link in the very first post of this thread, creatted by KKOSSEV is the same as the driver I have installed, that you say it is Gassgs fork.
A question that doesn't need answers:
Why is Hubitat community so confusing?!?
Sounds like a question not about the Hubitat Community (the forum) but for the specific author who forked the driver without actually changing any of the code. If they have a topic (thread) created for the release, you could ask there.
That being said, if you're still wondering about the firmware version thing, that data is normally provided by the platform for Zigbee devices, nothing in control of the driver -- so that's unlikely to change anything. A configure or re-pair (don't remove, just reset the device and re-pair; this is also one way it will definitely have your selected driver on pairing) might make it try this again. Otherwise, what platform version are you on (Settings > Hub Details)? I can't remember if this is a piece that was accidentally removed on early 2.4.0 versions.
(EDIT: "Tuya Version" would not be one of these fields; that would be the driver. I meant things like "Firmware MT.")
1 Like
The intentions were good here - Krassimir was just trying to do Ggasgs a solid by helping promote his fork of Krassimir's (original) driver.
If think the 1st post spells it all out pretty clearly - both versions are linked there. Gassgs created his fork based on the outsized popularity of this particular mmW sensor - it was simply intended to be a slimmed-down version of Krassimir's driver (which covers many more mmW sensors than just this model).
I can confirm sensor purchased from Amazon direct from seller "linptech" end of March 2025 came with firmware v1.0.6, as reported by kkossev's "Tuya Zigbee mmWave Sensor" v3.4.1.
Thank you @hydro311 for your quick reply and help.
1 Like
Ok sorry everyone, I know I'm really late to the party on this, but is it weird that the built in driver only shows this as a motion sensor, not a presence sensor, as well as its not reporting any Firmware versions. I mean it seems to be working well with the built in driver, but I feel I'm missing out. TYiA.
mmW sensors always use the "motion" attribute (not just a Hubitat thing - I think that's true on all automation platforms).
The "presence" atribute is reserved for home-vs-away sort of stuff, since that concept has been around for a much longer time than mmW.
2 Likes
ok that makes sense, but then why is it only acting as a motion sensor and not a presence sensor? Should I use a different driver instead?
It is not a presence sensor, it is a motion sensor. It does not tell you when you are outside the house, which is presence. It detects movement inside the house with mmWave.
Don't take too much from how the company has named the product, there is a trend to differentiate mmWave sensors from the standard "PIR only" sensors by using the word presence, but it means nothing in the Hubitat world, it is just how it is being marketed.
It is based on the idea of "occupancy" which means someone is present in the room, which it does detect, but it detects the presence of people by using Motion, so it is a motion sensor.
2 Likes
Thank you for the clarification! Do you have a presence sensor you recommend. I ultimately just want a sensor that can tell when I'm sitting at my desk to turn on lights, then senses when I leave to turn off lights. I have the Aqara FP1E but it seems to only work in a similar fashion of motion detection.
The Linptech can do exactly what you want...does that for my wife in her office. I use the Linptech along w/a standard motion sensor as the standard sensor has a somewhat faster turn-on than the Linptech, something my wife values. The Linptech does an excellent job of sensing her at her desk even when she is sitting still/moving infrequently. Once properly configured in terms of sensitivity I think you'd be quite happy w/the results.
True presence sensors don't operate at room level (not that I've seen, anyway), they are more about sensing if your in your home or not, rather than being in a specific room.
You could consider a pressure sensor on your chair that would tell exactly when you're in your chair or not, but if you're not in your chair (got up to do something in your office, walked into your office to find something and not sitting down) then you would not be marked present in the room, lights would not come on or turn off.
2 Likes
I have one Aqara FP1E and five Linptech/Moes. One of the Linptech is on the wall behind my desk in my office. It knows I am at my desk no matter how still I am or for how long.
My Aqara is one of three in my main room, and it fills a blind spot from the other two sensors, which are Linptech. It seems to hold presence well. It gets the edge of the couch where my Beagle sleeps, and it stays active when he is the only one in the room.
MmWave detects micro movements and it detects through materials (I read that they can actually see your lungs expanding and your heart beating as movement),
So they are great for sitting at a desk. A PIR sensor would not see my hands moving since the keyboard is slightly under my desk on a drawer, and I probably go several minutes while working without moving my head much. It goes inactive in 10s otherwise, when I leave. My office automation motion controls the office ceiling lights, two lamps, my desk led strip lights, and a fan.
1 Like
Yup, we've had posts here about the Linptech sensing through walls, including from me. I had to put a small piece of metal behind two of my sensors mounted on walls, as they were sensing motion in the room behind them on the other side of the wall. These types of sensors, unless they have built-in sheilding, can sense in multiple directions, including behind themselves.
I do appreciate all the help!! But I keep coming up with more questions as to why its not working for me then lol.
Below are my settings an someone please tell me if I've done something wrong. Because my automation will still turn off my lights because of lack of "motion". TYiA you are all amazing and this is why this community is so great!!
I don't use the built-in Linptech driver, but is your set detection distance (5 ft) enough - how far away are you typically from the sensor?
Which driver do you use? Yes I have above me about 4 feet away, but I was just messing with that and I upped it to 10 feet and it seems to be going inactive less, but it still does, its not even sensing my typing or mouse movements.
I usually have the opposite problem, where if I use high for both settings my lights never turn off. These have to be tweaked in for position and sensitivity.
Still, your current states are incomplete, you should have more than just motion, even with the built-in driver. The device may not be paired correctly.
You realize you are in a community driver release thread, but you are using and asking about the built-in driver? You really should use HPM to install the community 24GHz driver posted here, or scroll to the top and get the driver code and paste it in.
Change to that driver in device info, and press configure, and then you will actually be talking about the driver this thread is about if you have any issues. You may want to reset the device and pair it again before changing to the new driver, just in case.
3 Likes
AHHH!!!!! The new driver seems to be working so much better!! Thank you so much for the guidance!!!!
1 Like
1 Like
