© Screek Workshop

RedditFacebookXYouTube
Screek Workshop
/
🦋
Human Sensor 2A(LD2450)
/Beta Firmware For 2A
Beta Firmware For 2A
Beta Firmware For 2A
Beta Firmware For 2A

Beta Firmware For 2A

  • How To Guide
  • Acknowledgments
  • Beta Release
  • V240426_1_BETA
  • V240109_1_BETA
  • V230908_3_BETA
  • V230908_2_BETA
  • V230908_1_BETA
  • V230906_1_BETA
  • V230905_1_BETA
  • V230902_1_BETA
  • V230829_1_BETA
  • V230828_2_BETA
  • V230828_1_BETA
  • V230823_1_BETA
  • V230818_2_BETA
  • V230818_1_BETA
  • V230810_2_BETA
  • V230810_1_BETA
  • V230807_1_BETA
  • V230806_3_BETA
  • V230806_2_BETA
  • Older Version
  • Tips
  • Regarding icon schematics In Release Note
  • Adjusting parameters using the device's Web page
  • What’s my current version?
  • Troubleshooting
  • LD2450 Current Limitations
  • Alternative Downloads
  • Page not opening during OTA upgrade

How To Guide

How-To: Updating firmware file for 2AHow-To: Updating firmware file for 2A

Acknowledgments

Firmware 2A has received a lot of suggestions and direct code contributions from many people, and we've tagged them directly in the changelog. We apologize for any lists that may have been missed.

Here is a list of additional acknowledgements

  • LaneaLucy@Reddit: Provided a keep-it-sent mechanism for the light sensor so that it pulls light to the HA at least once a minute.

Beta Release

⚠️
In an ideal world, sensors wouldn't need frequent firmware updates to ruin your beautiful automation setup with hassles and redundant unanticipated behavior. So, if everything is working well, weigh whether you want to try Beta firmware.

V240426_1_BETA

Direct Download

CHANGELOG

  • Extend the maximum timeout to 1800 seconds. (Thanks to Stefan Hampden for his feedback)
image

V240109_1_BETA

Direct Download

CHANGELOG

  • Based on forum feedback, we have increased the maximum value of the Y coordinate to 7500, previously it was 6000.(Thanks to Gus, Shaq and others on the HA forum for suggesting this.)
image
  • Some Zone info information is now hidden by default, with adjusted levels for better compatibility with HA 2024.1(Thanks to Marco Zambon for the feedback. And TheZoker for the patch.)
  • ⚠️
    Because of the property realignment involved, if your info is still a black entry after the update, you may need to re-add the sensor.
image
  • ESPHome kernel is now using 2023.10.(We're testing the latest 2024.12 kernel situation and will probably migrate over in the near future.)
image

V230908_3_BETA

Direct Download

CHANGELOG

  • 🧬Added target angle display, orientation and position status display. (It got the idea and key code from walberjunior.)
  • notes from walberjunior:

    I added direction, position, angle (not very accurate but can be useful in some cases) and a general threshold for presence.
    image
  • 🧬Added a Zone global switch that can be turned off when the Zone feature is not needed. This may reduce the number of zone triggers if there are too many people.
image
  • ⚙️Adjusts the icons for target X and Y.
image

V230908_2_BETA

Direct Download

CHANGELOG

  • 🐞Fix a timeout mechanism on startup that could cause a presence state to flip, including showing that there are still no people in the region when the target number is 1. (Thanks to haip for the feedback and the code idea).
  • 🐞Fixed the problem that the state could not be initialized due to the delay at startup (display unknown).
  • ⚙️Adjusted back Any-Presence Timout spelling error.
image

V230908_1_BETA

Direct Download

CHANGELOG

  • ⚙️Moved some of the less frequently used elements of the settings screen to the debug paragraph.
💡
Due to the modified properties, if a duplicate element is displayed, it can only be disabled or the sensor re-added. We try to minimize such operations on the stable version.
image

V230906_1_BETA

Direct Download

CHANGELOG

  • 🐞Fixed an issue where repeated triggers on the way to a delayed shutdown would not interrupt the cancel.Added Any Presence Timeout.(feedback from haip, code contributed by athua.)
image
💡
Our most recent update(since V230823_1_beta), due to a grammatical error in changing a name of a core attribute from humen to human, has resulted in a potential breakage of the old front page cards as well as the automation process to go back and adapt and modify them. Through feedback from Emmanuel Gelinotte, we realized the severity of this issue, and since the firmware has already been updated a couple of versions ago, we'll just have to go ahead and maintain this new change.
image

V230905_1_BETA

Direct Download

CHANGELOG

  • 🧬Added Any Presence Timeout.(feedback from ferbulous, code contributed by athua.)
💡
What it does is, when any target disappears, it needs to delay the disappearance.
image

V230902_1_BETA

Direct Download

CHANGELOG

  • 🧬Add a timeout function to each zone area, when a delay is set, the target leaving needs to reach a specified number of seconds before it becomes disappeared.(Code contribution from athua)
image

V230829_1_BETA

Direct Download

CHANGELOG

  • ⚙️ Extend the left and right coordinates of the X-axis to 4m.(Thanks to athua for the feedback).
  • ⚙️Fixed Y max coordinates of zout to max 6m.(Thanks to noname.essqq and athua for feedback).
image

V230828_2_BETA

Direct Download

CHANGELOG

  • 🧬We've noticed that sometimes it's more puzzling to accidentally enter cases where the start area is smaller than the end area, especially negative numbers. We've added a dynamic region setting input hint that will help you check for potentially invalid inputs.
  • To make it easier for you to check the validity of the coordinates, especially in the case of negative numbers that violate the intuitive sense of size. We have added a quick check.
  • ⚙️ Adjusted the order of initialization information at startup to reduce the appearance of unnecessary unknown target presence attributes.

V230828_1_BETA

Direct Download

CHANGELOG

  • 🐞Fix not entering area detection when the target's x-axis coordinates are negative.(Thanks to walberjunior for the code)
image
  • ⚙️Limit the detection distance of the X-axis to 3m left and right (thx to walberjunior for the code).
image
  • ⚙️Optimize the last light update logic to ensure that switching fast update mode does not cause a delay in the update. (Thanks to rob_sm7219 for the feedback)

V230823_1_BETA

Direct Download

CHANGELOG

  • 🐞Fixed that if 2A starts with 0 light, it will show unknown unless there is a light change. (Thanks to rob_sm7219for the feedback)
image

V230818_2_BETA

Direct Download

CHANGELOG

  • 🧬The light sensor can be set up with an update strategy that allows you to choose faster updates, and if you choose the faster strategy, it will push whenever there is a change per second, even if it's a 0.1lux difference.(Thanks to rob_sm7219 for feedback).
  • We received feedback that we wanted the light sensor to work more aggressively to capture changes in active scenarios like indoor curtains.
image
Light Update Config For 2A
  • ⚙️Move the infrequently used ESP Reboot from the Config property to Diagnostic. (But need to remove re-add sensors to exhibit this behavior)
image

V230818_1_BETA

Due to a file caching issue, V230818_1_BETA was cached for an older version that we uploaded and changed the version name to V230818_2_BETA. We are very sorry for this inconvenience, please download V230818_2_BETA.(Thanks to dm_me_somethin_silly, vladijane for their feedback.)

V230810_2_BETA

Direct Download

  • 🐞The units of speed for Target 1, Target 2 and Target 3 are now harmonized into m/s, And the units were converted correctly, it will now show a correct unit for speed.(Thanks to txwindsurfer, Touchit88 for the feedback)
image

V230810_1_BETA

  • ⚙️Update the ESPHome kernel to 2023.7.1 .
image

V230807_1_BETA

Direct Download

  • ⚙️Reducing Any Presence to its earliest name will logically count the exclusion area, and if it's in the exclusion area, then it won't count. (Thanks to Rock--Lee for the feedback.)
  • icon
    Rock--Lee reminds us of a very serious issue, these name changes can cause the associated automation to fail. So if you might need to check to see if this property is being used, we'll avoid changing these basic names afterward.
    Go back use the old name, and it no will not consider the
    Go back use the old name, and it no will not consider the
  • 🐞Fixed Zout1 Presence status being true all the time, (thanks to Emmanuel Gelinotte for the feedback).
Fix this wrong state
Fix this wrong state
  • ⚙️Removed potentially convoluted tolerance settings.(thanks to Thomas Nonato Beck)
No more tolerance.
No more tolerance.

V230806_3_BETA

Direct Download

  • 🐞Fix the problem that the X endpoint coordinates of region 3 and region 2 are correlated with each other. Region 3 should now work correctly.

V230806_2_BETA

  • 🧬Considering the needs of some people, we have added a region exclusion feature that currently supports an excluded region 1, It is called Zout1, which stands for Zone-Out 1.This is a very preliminary feature, so please give us feedback if there are any issues.
Zout1 State
Zout1 State
Zout1 Config
Zout1 Config
  • 🐞Fix an issue where the region counts for regions 1, 2, and 3 may be incorrect.
  • ⚙️Adjust Flash save interval to 5 seconds, as configuring these parameters can be very laborious.
  • ⚙️For those of you who use the web interface to adjust parameters directly, we've moved Uptime to the top and now have a more centralized place to set coordinates. This approach is great.
Uptime
Uptime now on top, become ESP Uptime.

Direct Download

Older Version

Older Version

Tips

Regarding icon schematics In Release Note

Our definition of them is:

  • 🐞 = fixing problems, bug metaphor.
  • 🧬 = new feature
  • ⚙️ = tweak internal settings

Adjusting parameters using the device's Web page

The introduction of zones leads to many setup parameters. The interesting finding we got from our users is that it may be much more intuitive to set it up directly from the web interface.

image

One of the easiest ways to get to your device's web page is from the Home Assistant's Device Properties page, click the VISIT button.

image

What’s my current version?

You can easily find the current version number at the bottom of the sensor's device properties page.

image

Troubleshooting

LD2450 Current Limitations

The current LD2450 firmware (v1.22, V1.23_beta) is always locked to an active target, and Hilink says it will make new firmware available in the near future (August) that will allow switching between multiplayer and single target modes. The behavior of the single person mode is similar to the LD2410, which will track a single active target. We look forward to Hilink's new firmware for multiplayer performance.

Alternative Downloads

  • Download From DropBox

Page not opening during OTA upgrade

icon
There are some such times when you opt for an OTA firmware update, go some progress and then the page becomes inaccessible. The reason for this is usually because the connection is slow while the update is going on and the sensor is processing the update and updating its own sensor data at the same time, resulting in an interruption of the update's internal service. This seems to be a long-lasting issue with the ESPhome system. The solution is also simple, place the device (phone, computer) doing the update as close to the router as possible and the sensor as close to the router as possible. With a better signal, the update will be done as fast as possible.