Real-Time FAQ

• I'm not familiar with ESPHome, can a wizard tell me how to connect it?
• Why are there so many models of Series 1?
• What is the difference in use between the models?
• What are the differences between the models?
• Difference between radar modules LD2410B and LD2410C?
• After I connect the firmware, there is both a Bluetooth sensor in HomeAssistant and a WIFI connection, which one should I choose?
• I tried to do an OTA update, but after a certain progress, the page always loses connection and retries many times as well.
• The sensor looks hot, it has no cooling holes, should I be worried about that?
• In the logs, I've seen some information that says the energy value unit can't be a percentage.
• Why do I need or want the android(or IOS) app?
• Do I need the yaml source? It seems to be working just fine as is. Is this just if I want to tinker with it?
• The ESPHome firmware version shows up as Unknown does this mean I need to update it and if so where can I find any docs telling me how to do so?

I'm not familiar with ESPHome, can a wizard tell me how to connect it?

You don't need to have any special knowledge of ESPHome, nor do you need to have the ESPHome addon installed, the sensor uses ESPHome as the architectural technology. You just need to configure the network and then it will be automatically found in HomeAssistant, click on it to add it. The process is seamless.

Also. There is a detailed connection guide on our documentation site (https://www.screek.io/1u/getting-start/).

Why are there so many models of Series 1?

They are mainly branching out into multiple models for different form factors, and they are our attempt to diversify.

What is the difference in use between the models?

They are the same in terms of usage and interface, and both support Bluetooth connection and WIFI connection.

What are the differences between the models?

If the firmware needs to be completely wiped and rewritten, then the ESP32-S2 sensor (currently only 1U) will need to be put into DFU mode, as well as not being able to support ESP WEB TOOL to do so.

Difference between radar modules LD2410B and LD2410C?

• They are two different sizes, but the same functionality.
• The LD2410B is rectangular to be a bit longer, while the LD2410C is closer to shorter in the positive direction and a bit wider.
• They are approximate in price.
• The solder pins for the connections are different, the LD2410B is a 1.27mm pin while the LD2410C is a 2.54mm pin.

After I connect the firmware, there is both a Bluetooth sensor in HomeAssistant and a WIFI connection, which one should I choose?

• Bluetooth has a shorter range and is limited by the location of your Bluetooth adapter.
• WIFI on the other hand has an unlimited distance.
• If possible, we would recommend the WIFI connection in preference.

I tried to do an OTA update, but after a certain progress, the page always loses connection and retries many times as well.

In our observation, due to the update mechanism of ESPHome, it needs to complete the update in a very short period of time, if the sensor is far away from the router and the transmission rate drops, then the sensor has to deal with other tasks at the same time for too long during the OTA update, which may lead to the OTA system running down, and also produce the page losing connection.

Placing the sensor as close as possible to the router and then updating it will avoid this.

The sensor looks hot, it has no cooling holes, should I be worried about that?

The heat comes mainly from the radar module LD2410C, which generates a lot of heat when it's working.

In a recent firmware (V2023_0704_1 and after) we adjusted the processor running strategy, and the WIFI mode, and in this new firmware we found the operation to be stable.

In the earlier 1U, we designed the case without heat sink holes, which would lead to some heat buildup. But as long as the new version of the firmware is used, the temperature difference is just a few degrees difference in our tests, which does not cause a big problem.

In later versions(1u-box-b) we added heat sinks to the housing, they are less aesthetically pleasing but will dissipate some heat.

In the logs, I've seen some information that says the energy value unit can't be a percentage.

This is a known issue that doesn't affect usage and usually just shows up in the logs when registering the device and connecting for the first time.HomeAssistant's most recent update puts tighter restrictions on units for device types. We'll address this in the next firmware update.

Why do I need or want the android(or IOS) app?

(from Unthred@HA Community)

app is for adjusting parameters. When the default parameters aren’t very satisfactory, like some fixed interference at specific locations in the scope (mainly the fan ones), then setting a different sensitivity might help. We’re in the initial stages of refining an FAQ and hope to gather more interesting information: 

Do I need the yaml source? It seems to be working just fine as is. Is this just if I want to tinker with it?

(from Unthred@HA Community)

if you’re just using it to implement sensors, then it’s probably not needed. You just need it to work. yaml is for people who want more customization to add certain things they want to customize.

The ESPHome firmware version shows up as Unknown does this mean I need to update it and if so where can I find any docs telling me how to do so?

(from Unthred@HA Community)

this is a known issue that can arise from not relying on esphome to be able to import, and we don’t have this type of import feature turned on: one reason is for unfamiliar users who might accidentally let the sensor brick, and the other is for those who have more need to always be able to compile our yaml on their own at any time. what we want is to find the simplest balance between letting We wanted to find the simplest balance that would allow us to make it accessible and easy to use, temporarily hiding it from the overly complex and jargon-ridden side of Home Assistant, and introducing it in the easiest way possible. With the advantage of local vendors, it’s possible to quickly try to integrate some DIY sensors into the HomeAssistant system at a reasonable price, and we’ve enjoyed exploring this idea.

since the esphome version number always follows the version number of an esphome firmware and can sometimes be confusing. In our experience, if it's not a very important update, always timely constant updates may not always gain a lot of benefits. Many commercial sensors, after all, may not be updated for five years. So adding the attribute 'Screek Version' to many of our DIY sensors, which is used to identify when we last compiled the firmware for that sensor, makes it easier to decide if you need to update it, or to understand what has happened with the update. It's still a trade-off, we want to preserve the power of esphome and accommodate enthusiasts who don't need to know more details about esphome. And for those who in turn love to modify their own sensor configuration, our yaml source code will surely give it fun in another direction.