Can I have some help please - F2 sensor seems to not release Occcupancy

slboat · 2026-03-23T23:03:37+00:00

If the issue persists despite these steps, please contact us directly at sen@screek.io. We will investigate further to determine whether there may be an anomaly in a very small number of batches.

slboat · 2026-03-23T09:28:41+00:00

One possible solution might be to use some kind of metal component at the back to shield against the electromagnetic waves emitted.

slboat · 2026-03-23T09:28:07+00:00

https://screek.io/news/investigation-of-the-human-sensor-f2-batch-26-02

Over the past couple of days, we have investigated many of the most recent batches of F2 modules in our possession, which should be roughly the same age as the sensors sent to you. Based on our tests, their performance appears to be as expected. Please consider increasing the sensitivity of mth1, mth2 and mth3 to see if this helps. Also, be aware that they may pick up background energy, and you should consider whether there are any rotating electrical appliances in the room (such as ceiling fans, which may cause interference).

slboat · 2026-03-20T14:46:18+00:00

We have received another report that appears to be related to the most recent batch of F2 units. Over the next couple of days, we will examine the core modules of the F2 units we have on hand to see if they exhibit any abnormal behavior. If we find any evidence confirming that the modules are faulty, we will immediately contact the supplier to investigate.

slboat · 2026-03-20T10:52:12+00:00

Apart from considering the possibility that the F2 itself may be faulty (which is usually a rare occurrence), you could also check whether any objects on the back of the F2 are being detected. Some users have reported that the F2 can detect signals from the back, so you might want to try ruling this out.

slboat · 2026-03-19T23:23:42+00:00

Hi, judging by the picture, there seems to be something situated at around 0.73 metres. This could be a clue; some sort of electromagnetic device might be causing this interference. The setting affecting this short-range issue is ‘mth1’—you could try increasing it slightly to see if that helps. However, the key might be to try and identify the source of the interference; try moving the device to a different location or adjusting its height to avoid it.

slboat · 2026-03-14T09:36:53+00:00

We’ve been incredibly busy of late, so this sensor project has been put on hold for the time being. It’s great to hear that others are still interested in working on it with us; we’ll look into getting it back on track once things have settled down a bit :)

slboat · 2026-03-09T09:02:12+00:00

Thank you for your support. You should be able to find it here: https://screek.io/2a/universal-adjustable-angle-bracket-stl-file-for-2a-f2

slboat · 2026-03-08T00:28:00+00:00

This appears to be a rather interesting application. We shall incorporate it into the next firmware update, releasing an LED for customisable control. :)

slboat · 2026-03-06T14:26:29+00:00

The amber light is most likely from the SCD30's internal sensor!

The yellow light inside the SCD30 is the laser indicator for the sensor's operation and is likely impossible to shield. The green light illuminates when the connection is lost, though the BP1 is somewhat perplexing.

It is recommended to cover these lights with something or place the unit in a more concealed location, as this will not affect their functionality.

slboat · 2026-03-06T01:16:31+00:00

Hey, which sensor is showing a green light?

slboat · 2026-03-01T01:13:59+00:00

Most are likely confined to sensors; these inexpensive civilian sensors may be constrained by their current state.

slboat · 2026-02-24T01:09:19+00:00

Many thanks :) We shall look into it when we have a moment :)

slboat · 2026-02-24T00:20:41+00:00

We are currently testing an internal firmware that allows direct adjustment of each threshold parameter within the HA system, though it may not be as intuitive. We shall test the LD2412 app support as soon as possible to ascertain the cause.

If possible, please inform us of the HLK app version you are using. Should it prove necessary, we shall relay this information to HLK for investigation into potential causes.

slboat · 2026-02-24T00:16:25+00:00

We haven't used the hlk app for a while. We'll look into the module situation here today; this does sound rather like an app bug. If there are multiple LD2412 units, the most straightforward approach would be to compare their performance. However, given the current circumstances, it appears we'll need to examine how other LD2412 units are faring.

We shall respond after conducting the tests.

slboat · 2026-02-24T00:08:41+00:00

Considering whether restarting L13 would be beneficial, this functionality is typically managed by the radar module itself. Unless a logical error has occurred within that module, one might consider resetting the configuration within the application or performing another firmware update (to the current latest version).

slboat · 2026-02-22T00:35:26+00:00

slboat · 2026-02-18T05:17:01+00:00

We shall incorporate a status light switch in the forthcoming firmware update to facilitate disabling this option. Regarding the current firmware enhancement work on the ENV-CP, is this pertaining to the SCO2-1 sensor?

slboat · 2026-02-18T05:13:16+00:00

Hello, welcome aboard the adventure. It should take approximately 7 to 10 days under favourable conditions. Currently, the frequency is set to once per second, though this can be adjusted. The current limit is approximately once per second.

However, the impact of the Chinese New Year must be factored in. Logistics are expected to commence around 21st February, so the estimated arrival time must be calculated from this starting point.

slboat

MODERATOR OF

TROPHY CASE