-
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
Auto disable WiFi #4330
Comments
It would be useful to turn off the wifi in the t1 touch sonoffs installed in the bedroom near the head of the bed, so that during the night you avoid having additional wifi waves, of course maintaining the functionality of the switch. As soon as the button is pressed, the wifi is re-locked and then automatically disabled. Thank's |
Hi, It is not good to have a wifi source over the head. I agree. Your device needs to be installed in another place. But also, turning off the wifi of your smart device make it not a home automation device. That is out of the scope of Tasmota. Sorry. Please see readme for more information. |
Another thing you can try. Besides changing the place of your device, is to set wificonfig to 5 and when you don't want your device to use wifi just turn off your wifi router. With that configuration, if there is no wifi, your sonoff will be looking for a wifi signal but will not transmit anything. As soon as your wifi router is turned on, your device will connect again. |
Thanks for the reply. I am aware that having a device without wifi is not a home automation device, but the fact that I have replaced all the home switches with t1 and to have a uniform appearance I also needed two switches near the bed. My idea was that when I press the button the wifi turns on, sends a mqtt switch to another relay. Then once done, the wifi can be switched off. The same thing to make the doorbell ring sound from the bed. |
Yes, understood. I think you need another type of hardware for what you want or another type of switches. Wifi signals close to your head is not good. One idea could be to have a normal switch (or a capacitive one if you like) close to your bed but wired up to your roof light (far from your head), and in that place, put a sonoff basic, or a shelly, or a nodemcu connected to your switches. And that device can have Tasmota and wifi. Remember, if you want, you can turn off your router and all your wifi devices will stop transmitting. Also, you can see #1805 and #3609 If you have further questions or ideas, please do not hesistate on asking here or in the Tasmota chat. Thanks |
Or using a RF433 battery powered wall switch, and sonoff rf bridge. My problem is find a similar touch t1. But modem sleep can be considered? Thank's |
Excellent idea.
Modem sleep is already implemented in Tasmota if it is compiled using core 2.3.0 (the actual precompiled bins) or the actual arduino stage core. (sleep is not enabled for core 2.4.0, 2.4.1, 2.4.2 - those core hungs with sleep) But modem sleep is the light_modem_sleep that will put the cpu to sleep (less power) for up to 3 DTIM and then it will wake up for receiving and transmitting from the router. So, the sleep feature just reduce the CPU energy consumption, but the wifi signals will stay there. If you set sleep to 1 (using command sleep in the console), your Tasmota device will use less energy to work and all the functions will work fine. If you increase that value up to 200 ms for example, all functions will work, but you will notice a delay in response when pressing any button. |
I was thinking about it, but because it would not be useful to have the possibility of having an autodisable wifi after x seconds after launching a mqtt command. If you think of a device sonoff t1 that acts only as a button to turn on remote relays in toggle mode. It would work similarly to an RF433 remote control. If you need to change the configuration of the sonoff t1, it would be enough to increase the autodisable time to 5 minutes and you would have all the time to configure it. Each time you press the toggle button the wifi will turn on anyway for 5 minutes. Thanks again for your patience Greetings |
So you seriously want a switch that once toggled has to re-connect wifi taking at least 5 seconds and then performs the action you want. That means it has to store these actions and execute once connected. That's a whole new ballpark. Why not buy these https://www.itead.cc/smart-home/t433-sticky-rf-remote.html and have a bridge somewhere to execute your requests. |
I had not calculated the connection times of the wifi at least 5 sec. Ok i try to buy it Thank's |
I would also be interested in this feature, mainly to safe power if WiFi is not required. |
Now it is available the command |
It is possible to turn WiFi automaticlly on again? As Example at a specific time or after x hour? |
Yes, by the use of rules and the new command. Please check the docs for more information about rules. If you need further assistant on that, please address this to the Tasmota support chat. Thanks. |
Thanks you too |
Thanks, but I have flashed the latest development version (9.3.1.1) using Tasmotizer and choosing the development release, but the console says "{"Command":"Unknown"}" if I try and use the WIFI command? |
Same there - no idea how to use "wifi" command. Nothing in documentation... |
I would be interested in the feature to reduce WIFI signals during the night. Did someone find the documentation or could provide it here? |
Have you read |
Hi, it is documented in the Tasmota Oficial Docs. Please go to: https://tasmota.github.io/docs/Commands/#wi-fi Thanks. |
Have you look for this feature in other issues and in the wiki?
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
(Please, remember to close the issue when the problem has been addressed)
The text was updated successfully, but these errors were encountered: