-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
make tasmota less chatty on battery operated devices #8044
Comments
Did you tried to play with logs settingsto see if you can reduce the traffic? |
That was a bit quick to close. Could you please reopen? |
Functional to tell the broker we're back in business
This message can be disabled by command
These messages will be disabled on DeepSleep wakeup detection released today
Functional
This message can be disabled by command
Can already be disabled with
Functional
This message can be disabled by command
Can already be disabled with
Functional
Can already be disabled with |
Hello Theo, Thanks for picking this up. And even providing the fix at such short notice! Much appreciated. |
Have you looked for this feature in other issues and in the docs?
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)
I am experimenting with Tasmota 8.2 on a Earykong TYMC-1 Door Window Sensor
(https://templates.blakadder.com/TYMC-1.html)
After installing it successfully I monitored it in node red and noticed that on every event (door open or door close) the device emits 13 messages. See the example below
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494tele/tasmota-0138/LWT : msg.payload : string[6]"Online"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494cmnd/tasmota-0138/POWER : msg.payload : string[0]""
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494tele/tasmota-0138/INFO1 : msg.payload : string[117]"{"Module":"Tuya MCU","Version":"8.1.0(tasmota)","FallbackTopic":"cmnd/DVES_60E08A_fb/","GroupTopic":"cmnd/tasmotas/"}"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494tele/tasmota-0138/INFO2 : msg.payload : string[80]"{"WebServerMode":"Admin","Hostname":"tasmota-0138","IPAddress":"192.168.71.237"}"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494tele/tasmota-0138/INFO3 : msg.payload : string[28]"{"RestartReason":"Power on"}"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494stat/tasmota-0138/RESULT : msg.payload : string[15]"{"POWER":"OFF"}"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494stat/tasmota-0138/POWER : msg.payload : string[3]"OFF"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494tele/tasmota-0138/RESULT : msg.payload : string[85]"{"TuyaReceived":{"Data":"55AA0005000501010001010D","Cmnd":5,"CmndData":"0101000101"}}"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494stat/tasmota-0138/RESULT : msg.payload : string[14]"{"POWER":"ON"}"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494stat/tasmota-0138/POWER : msg.payload : string[2]"ON"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494tele/tasmota-0138/RESULT : msg.payload : string[85]"{"TuyaReceived":{"Data":"55AA00050005030400010213","Cmnd":5,"CmndData":"0304000102"}}"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494stat/tasmota-0138/BATT : msg.payload : string[4]"high"
3/31/2020, 6:03:54 PMnode: da8b81ba.a7494tele/tasmota-0138/RESULT : msg.payload : string[51]"{"TuyaReceived":{"Data":"55AA0002000001","Cmnd":2}}
Many of these messages are not needed in normal operation. Basically only the stat/topic/POWER messages would suffice.
The extra messages make the device less reliable, as it needs to transmit in a limited time, before it goes to sleep again. Moreover, it is an extra battery drain (however limited it might be)
It would be great if there is a mode (battery mode) that switches off these excess messages automaticaly, or a console command to do so manually
Kind regards,
Bert Haverkamp
The text was updated successfully, but these errors were encountered: