Frient Motion Sensor and Frient Motion Sensor Pro Review 2022

Tested the motion sensors of Frient.

I must say I was impressed. They are not expensive, yet good quality and reliable.
The sensors are able to reach long distances and don’t get disconnected easily.
However, I realized that the Pro version actually doesn’t bring much added value to Smartthings Hub owners, since the illuminance and tamper functionalities don’t work. Therefore, the only additional benefit you get is temperature.

I currently have 3 motion sensors and 1 pro motion sensor working. Getting fan…

1 Like

I believe there are more features in the works for the Pro versions

Hi @RBoy

I hope so. I mean, I think for the European market this is one of the best brands right now based on the wide range of device types, price and quality.
Potential is there, so let’s see if they keep the momentum

How are you finding the response time of the frient motion sensor?
Some of the Amazon reviews claim it’s very slow.

I just started using the Pro version in my kitchen. The tamper and illuminance features are now supported by the Frient driver but not the Smartthings driver. It took a few pairings to get everything working, but now, apart from one thing, it is working well.

The one thing is illuminance reporting. I use it to turn on the lights after motion is detected, but only if it is dark. Unfortunately, illuminance sometimes does not update for hours, and it relies on the last reported value. That means, in the morning it might activate after it doesn’t need to. In the evening, it might not activate when it should. When the lux level is in range, it works very well.

I cannot find any way to get support from Frient, which is very disappointing.

1 Like

I don’t know for sure, but a number of inexpensive Zigbee multi sensors don’t send any reports unless they are sending a motion detected report. So you only get a Lux level report if the sensor is also reporting motion detected. This is done to extend battery life, and obviously the manufacturer is making the assumption that it’s really being used as a motion sensor with some added features, not a true multi sensor.

Could that be what’s going on here? It would explain why Lux is reported on different time intervals. No motion event, no lux report. :man_shrugging:t2:

1 Like

Frient is hardly cheap. Also, there are lots of motion events happening between the updates, so I don’t think it is that. However, I wonder if you are on to something. On a Saturday with lots of movement through the kitchen, it appears to be reporting at hourly intervals. So, maybe it is set to update every hour, but only if there has been motion detected in that time. I can’t imagine why that would be the case, but it seems a possibility. I will have a look at the history in more detail to see if that is borne out when there is no movement detection.

2 Likes

It only saves a fairly limited amount of history, but this is what I have found out. I walked into the kitchen at 20 minutes past midnight this morning and the light didn’t come on. Looking on the app, it was still using a lux measurement from earlier that had obviously been taken when the kitchen lights were on. But, while I was standing there, the lights came on. I checked in the app and it had updated the light level, which had satisfied the precondition and switched the lights on.

That was the last motion for the night, and there were no light updates until 6.41, but there hadn’t been any motion detected before that…It then updated at 7.41 with no motion detected and has updated hourly so far today with motion being detected every hour.

Temperature seems to update hourly whatever the motion detection situation.

My conclusion is that there should probably be a light update every hour, but even that is inadequate as it may coincide with a lighting situation that is not representative of the current situation when it is used for a routine. It seems to me the only sensible thing to do is to check more regularly and also at any point when it is used by a routine. It uses two AA batteries, so it has plenty of power available. I am a complete beginner when ti comes to drivers, but would it be technically possible to change this behaviour with a custom driver?

With the exception of virtual devices, the primary thing an edge driver does is the same thing a printer driver does: send messages back and forth to the device.

Reporting behaviour is typically controlled by the firmware of the device itself.

The manufacturer may choose to control this behaviour with parameters (variables) that it allows users to set as part of “configuring” the device. But it may not. Devices with configurable parameters have to be smarter (which is more expensive), use up battery life faster, and typically add to customer support costs. So it’s a business decision, not an engineering one, and the first rule of home automation definitely applies: “the model number matters.”

Assuming the manufacturer HAS decided to make the reporting interval configurable, how does an edge driver author know what format those messages have to be?

With zwave devices, it tends to be pretty standardized, and device manufacturers typically publish a list of configurable variables and the acceptable values along with the conformance statement on the official zwave alliance website, and with newer devices, often in the user manual.

With Zigbee, though, it can be much harder to find this information and it may be done through proprietary methods, adding to the opacity.

So…the first step is to ask the edge driver author if there’s a way to configure the behaviour you want to change. They may have already researched that specific model and know one way or another or at least know some standard variables to try.

If they don’t already know the answer, The next step is typically to check the Home assistant forum, because those folks have usually gone very deep into pretty much every inexpensive Zigee device out there. (By “inexpensive“ in a Home Automation context, I mean non-commercial, intended for use in homes and apartments and sold individually at retail. So everything you use with SmartThings in most cases.) if they have a list of parameters and values, you can bring that back to the edge driver author, and see what they can do with it.

If there’s nothing in the home assistant forums, you can try contacting the manufacturer directly, but it’s often very hard to get these answers if they don’t already just publish them. Often times the company that brands the device didn’t actually do the engineering for it and may not have anyone on staff who even knows. (This is particularly true for Tuya made devices, but can also happen with other OEM’s.)

So the answer to your question is that it depends on what the manufacturer has made available for that specific model. Maybe yes, maybe no. You just have to start the research to find out. :thinking:

1 Like

Thanks, that’s useful to know. The only edge driver that works with all the properties of this device (tamper reporting, illuminance, temperature and motion) is the one from the manufacturer. Thing is, I can’t find any way to contact them. I will look harder!

2 Likes

They have a general email listed on their website, that might be able to pass you along.

Otherwise, sometimes you can get answers by posting on public facing channels like Facebook or Twitter/X. At least a marketing person will see it there and may also be able to pass it along. :thinking:

Good idea. I will give it a go.

1 Like

With my zigbee motion sensor Mc driver, everything should work except tamper.

Anyway, have you tried pairing it directly with the controller without making a change from one controller to another, so that it is configured correctly?

2 Likes

I’m not sure what you mean about making a change from one controller to another. I simply paired it with my Aeotec hub. Didn’t know about your driver. How do I access it? Tamper protection isn’t important in my kitchen!

At one point in the development of the new edge architecture, you could just go into the app, look at the device details, see the possible edge drivers that matched that fingerprint listed there, and pick the one you wanted. And you could use the same method to switch from one edge driver to another.

However, as of the time of this posting that method doesn’t always correctly configure the device, which is annoying. :rage:

So, instead, when you want to change to a different edge driver, particularly for battery powered Zigbee devices, you instead need to

  1. download the custom edge driver that you want to use to your hub and also remove any other custom edge drivers that would match the same device that might also be on your hub. So now there is only one custom edge driver on your hub that will match the device. (It’s fine if there are stock edge drivers, the custom edge driver will be given preference.)

  2. remove the device from your account altogether. Note that this might also remove any automations you had set up for it, so some people will add a dummy virtual device just to keep the routine in place. Others go ahead and delete the routines. That’s just a matter of choice. But again, annoying.

  3. now add the device back to your account and it should pick up the custom edge driver that you want to use and configure everything correctly. (As Mariano points out in his post below, sometimes you have to wait 30 to 45 minutes before using the new pairing will work because of a current bug in the SmartThings platform. If it doesn’t pair the first time, just wait for a while and then try again.)

  4. Now fix any automations that you had before you started all of this that were affected by the device being removed and re-added.

  5. finally, you can test the device with the new edge driver

——
This wasn’t the original intent of the architecture design. You were supposed to just be able to swap back-and-forth between different edge drivers in the app without affecting anything else. But it turned out that when you did it that way, devices did not get set up correctly, so now we have to go through all these steps.

3 Likes

When a device is directly paired with a driver, the necessary clusters and attributes are configured to inform all the necessary capabilities.

When you make a change from one driver to a different one, the device configuration is not performed and the one already made with the previously paired driver is maintained.
This can work or no work, depend of previos device configuration performed

On this channel link is my zigbee motion sensor Mc driver, which has worked well with that sensor for a long time, according to the users who tested it.

  • Install the driver on your hub
  • Uninstall the device
  • Delete the official frient driver
  • Pair the device and it should do it with my driver, if it doesn’t pair, you may have to wait about 30 minutes for the cache to update, due to a bug in smartthings, which we hope will be fixed one day soon.
2 Likes

. Didn’t know about your driver. How do I access it?

All custom edge drivers are downloaded in the same way.

  1. find the link to the channel invitation for the custom edge driver. You might get this from a post in the forum, from the author directly, or by checking the quick browse lists, in this case the one for sensors.

FAQ: Using the quick browse lists without the community wiki

Mariano has given you the name of the edge driver you will want to use, “zigbee motion sensor MC,” so you will find the link in the first post of his author thread:

(EDGE Driver-Mc): Zigbee Drivers for Motion, Open/Close, Moisture, Smoke-Co Sensors and others Devices - #4354 by Adel_Omar

(Mariano is a community member who has created many custom edge drivers that are very popular. When you see “MC” on the name of an edge driver, those are usually his initials.)

So you will follow the invitation link to his channel.
Subscribe to the channel.
Select the individual edge driver that you want downloaded to your hub.
Wait for it to appear on your hub. This usually only takes a minute or two, but sometimes it is longer.

Once it is there, you can follow the procedure I gave in my previous post.

3 Likes

Thanks for the info. I do know how to install custom drivers, I just needed the relevant link. I am sure it will be useful for others though. I will try it out later.

2 Likes

Was this not changed a while back so that the routine still remained with a placeholder for the deleted device which you had to edit again to get it working?

Or did I just dream that? Thought I’d even done this before.

1 Like

Admittedly it was last fall, but…

When I was updating some device firmware (first removing the device from SmartThings), it did leave a placeholder in routines. After the firmware update and re-adding the device, I simply had to go to each routine–best to make yourself a list of all of 'em that used the device–and “re-choose” a device for each placeholder.

Haven’t done that since last fall, so YMMV. Good Luck (in any event)! :wink: :wink:

2 Likes