-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Network Auto Heal schedule assistant / configuration option #3253
Comments
Frequent healing is not advised, it can actually have a negative effect on your network. I think the reasons mentioned here haven't changed: #3006. |
@kpine yeah I understand that. I've read somewhere that somehow, every night, ZwaveJs(UI) does an auto heal ... but absolutely not sure it is true or not ... what i'm looking for is scheduling it at a greater interval / different times etc ... @robertsLando and @AlCalzone : can you confirm there is a auto heal every night ? |
Never existed. As @kpine suggested this is generally a bad idea. If you really want to do it anyway you can use scheduled jobs |
I think OpenHAB used to do this in the beginning. We don't for the reasons mentioned above. |
so how i respond when ZWAVEJS UI shows my node heal status as "failed" but the log shows
|
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I would like to have an option to chose to activate auto heal network (from what I could understand reading here and there, it's active by default). Also, I would really like to have some sort of configuration to chose when to heal the network (scheduling).
The idea would be to avoid having the heal happening during times when my whole installation is susceptible to be in active use, and therefore avoid having lags / delays etc.
Also, I would prefer to be able to set the frequency at which that happens (daily, weekly, monthly).
Just throwing an idea here, maybe I'm the only one thinking about those things, I can get geeky sometimes :)
The text was updated successfully, but these errors were encountered: