Skip to content
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

Investigate determining the optimal route to a node ourselves #4477

Open
AlCalzone opened this issue Apr 18, 2022 · 1 comment
Open

Investigate determining the optimal route to a node ourselves #4477

AlCalzone opened this issue Apr 18, 2022 · 1 comment

Comments

@AlCalzone
Copy link
Member

Originally posted by @darkbasic in #4184 (comment)

Can't we brute force our way to a better route? Like automatically health-checking all the nodes in direct range from the controller (capable of reaching the target node) and then health-checking again each of these nodes to the target one? With such approach we can't go further than 1 hop without having to test insanely high numbers of combinations, but considering 99% of the targets can be reached in 1 hop that can be a viable option IMO.

@darkbasic
Copy link
Contributor

The link from Slack about dumb zwave route generation: https://forum.fibaro.com/topic/50752-zniffer-analysis-of-fgwp-102-mesh-update/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants