-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Command to switch Wi-Fi on and off in rules #5979
Comments
Closing this issue as it is duplicated (#4330). Sorry. Please, read the Contributing Guideline and Policy. Thanks. Support Information (Guide)See Wiki for more information. |
Please reopen this ticket. I had seen #4330 and had come to the conclusion that
Also I have read the policy. This is a feature request and not a "how do I..." type question. |
Hi, Sorry about the phrase "read the contributing....". Was not intended to you. As we have a lot of issues and requests, we use predefined answers. I forgot to delete that sentence. In fact, you did the feature request correctly and you did explain it very well. The request to have a command to turn off/on wifi was asked before and as pointed in the referenced issue, is not in the actual main goal of Tasmota. Anyway, that issue has the label: requested feature - hold over, for future reference and may be someone would work on that and make a Pull Request. So, it is not discarded but not to be worked on right now. |
Now it is available the command |
Hi there, I've tried the
|
Have you look for this feature in other issues and in the wiki?
Yes
Is your feature request related to a problem? Please describe.
I would like the device to connect to the Wi-Fi, fetch the time and maybe configuration, then switch off the Wi-Fi (e.g., during night time) and just execute rules locally. Upon device power cycling, it would connect to Wi-Fi again and the thing would repeat.
Describe the solution you'd like
A command to switch Wi-Fi on and off in rules.
Describe alternatives you've considered
Not using Tasmota for the task.
The text was updated successfully, but these errors were encountered: