-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Impossible to track more than one target #300
Comments
How far apart are the targets? |
I tested distances between 1 and 3 meters. Makes no difference. |
I just had the same issue. No matter the location of the two targets, one of them had to leave range for the other to show up. Resolved it by connecting with the HLKRadarTool app and enable the "Multiplayer" option that was off. Then both HLKRadarTool and HA could show two targets. |
Thank you, I had already seen that setting and turned "Multiplayer" on in the app, but it makes no difference for me, unfortunately. After two seconds (barely) of showing two targets the tracking starts alternating between them. |
Try factory resetting the mmWave sensor with the entity inside of HA |
That did it, thank you! |
Unfortunately the fix was only good for a short while. I was able to repeat the following several times (both targets are stationary in reality throughout the test):
***UPDATE after a few more hours of observation:
|
I have the same problem |
Same issue. The sensor does not do a good job tracking multiple targets despite being advertised as such. |
I also have a very similar issue |
I can track one target without problems. As soon as another target is present, the sensor displays both targets for not more than a few seconds and then only ever shows one target at a time, jumping back and forth between the two every few seconds.
I tested this behavior in different rooms and with different target locations.
The firmwares (mmWave sensor and device) are up to date (2.04 and 1.22). All device entities are enabled in Home Assistant.
The same erratic behavior can be observed in the HLK app.
The text was updated successfully, but these errors were encountered: