-
Notifications
You must be signed in to change notification settings - Fork 34
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
AHC: Proximity ignores Distance #88
Comments
Hey, could you paste this in your template editor and post the results here? This snippet filters all sensors of your proximity entity that is equal or less than 50 whatever ( ;) ) to your home.
|
Thank you for your quick response! Here is the result:
Please note that I'm currently home (and not far away anymore). |
Ok, could you check your history (graph) of all distance sensors of your proximity device when you were far away from home? |
Same error here. I was over 50km away, the distance in blueprint was set to 900m but it start to heat up... |
The problem is that the two distances are compared as strings, and not as numbers: so while |
Good point. Will check this an fix this soon. //EDIT: I'd just pushed an update with the fix. Feel free to test and give some feedback |
Works like a charm now. Thank you! |
Even though I'm currently hundreds of km away from my home zone (defined in the proximity section), every time I move towards it, my heating turns on. Expected behavior would be that my movements are being ignored when I'm out of the defined "Proximity Distance".
I tried different values for the "Proximity Distance" without success (so this does not seem to be a unit issue).
I'm running v 5.0.9
Here is my trace log: https://controlc.com/5f228328
The text was updated successfully, but these errors were encountered: