The LinkLink Emotion mmWave human motion detector looks interesting.
It works with Amazon Alexa so could I create virtual devices for the zones I create and have Alexa report when they go active/inactive as the basis for Hubitat rules?
1 Like
This depends on whether the zones can be used as triggers for Alexa routines.
Personally, if the intention is to use human occupancy as a trigger for Hubitat automations, I would get mmWave occupancy sensors that can be paired directly with Hubitat.
3 Likes
May not be bad if it works with Home Assistant.
I am skeptical about multiple zones detection. Aqara FP2 never works/worked in my case because near always it leaves ghosts. This way it is useless for automations.
1 Like
Just saw this video featuring it from Paul H. Sounds like the zone detection is local, and that it uses MQTT… Sounds like a good candidate for direct connectivity to Hubitat!
1 Like
I saw the video this morning and I've got my order in. Won't be delivered until the middle of next month, so plenty of time for me to read up on the whole MQTT thing.
1 Like
It will need an external MQTT broker.
I’m still not very versed in MQTT… I understand that there is some MQTT stuff in Hubitat, but not everything is supported.
MQTT is a "client / server" setup. Hubitat has MQTT client libraries. There are community apps written that use these libraries to connect to an MQTT broker (server).
The clients publish topics to the broker and subscribe to topics that other clients have published to the broker.
So two clients can only interact with each other via an MQTT broker. It’s the broker part that Hubitat doesn’t provide.
1 Like
I saw Hibbert’s YouTube too. I don’t use or have any real interest in Home Assistant. I’ve heard of MQTT but don’t know anything about it. From the above it seems MQTT needs something more, like Home Assistant, which leaves me out. Of course, I’d also want to know if this does or does or does not have the ghost issue like the Aqara
2 Likes
I feel like this mmWave sensor is the way to go, make zones locally on the device and have it trigger for each zone, so network chitchat is at a minimum as all the processing is done on the device itself and sends triggers to the hub only when needed in/out of a zone. Now according to Paul's video, it looks like it's pretty accurate, if that is the case and hoping that having multiple of these in a house does also work reliably, this could be a game changer for this type of sensor.
I think that newer mmwave sensors will be going in this direction and we will be seeing zigbee and zwave devices like this appear in the very near future.
Also a MQTT server can be run on any computer that is always on, no need for HA install anywhere in the picture for this to work with Hubitat, just need someone to write the driver for it using the MQTT driver already written to subscribe to the messages.
3 Likes
I've got this device on order, and I am now at the very beginning of learning about MQTT. I do already have a HA instance running so I figured I would just use the server plug-in for that. However, I'm happy to hear that there are standalone servers to run and I'm going to do a little dive on that. If you have any recommendations I'd love to hear them.
I'm also following this thread regarding an MQTT driver for Hubitat, in case you haven't seen it yet.
I have changed a MQTT listen driver to work with linknlink emotion. there still is need for a mqtt-broker. But it can now read/use the linknlink entries direct.
see GitHub - qwerk/linknlink-mqtt-hubitat: Use linknlink eremote via mqtt
4 Likes
Very new to hubitat, the box actually arrived today but wanted to get a motion sensor in my living room that could also controll IR
How would I go about getting this to work? Or can I connect the device directly to Google home and then have habitat import the device so I can add them to routines?
Thanks
