Rate limiting for MQTT?

[FrenkK]

I hacked a Tuya Smart Air by unsoldering their WiFi chip and soldering in a Wemos D1 with Tasmota flashed. The Tuya MCU module decodes the sensor data and it works.
The problem is, the updates are coming every second or even more frequently and this is bogging down my Homeassistant installation. Is there any way to simply send the MQTT update with the the last received value for all the sensors every minute or so? Having the option to average the values in between would be even nicer, the sensor data are noisy.

[FrenkK]

I solved this by going the other way. I used the Tasmota REST API to set up RESTful sensors in Home Assistant where I can set the scan interval.
This is the HA config that works for me:

rest:
  - scan_interval: 60
    resource: http://airdnevna.fritz.box/cm?cmnd=Status%2010
    sensor:
    - name: dnevna_humidity
      value_template: "{{value_json['StatusSNS']['TuyaSNS'].Humidity}}"
      unit_of_measurement: "%"
    - name: dnevna_TVOC
      value_template: "{{value_json['StatusSNS']['TuyaSNS'].TVOC }}"
      unit_of_measurement: "ppm"
    - name: dnevna_particulates
      value_template: "{% set particulates = value_json['StatusSNS']['TuyaSNS'].Illuminance %}{% if particulates > 0 and particulates <10000 %} {{particulates}} {%else%} {{0 | float}} {%endif%}"
      unit_of_measurement: "ug/m3"
  - scan_interval: 60
    resource: http://airpisarna.fritz.box/cm?cmnd=Status%2010
    sensor:
    - name: pisarna_humidity
      value_template: "{{value_json['StatusSNS']['TuyaSNS'].Humidity}}"
      unit_of_measurement: "%"
    - name: pisarna_TVOC
      value_template: "{{value_json['StatusSNS']['TuyaSNS'].TVOC }}"
      unit_of_measurement: "ppm"
    - name: pisarna_particulates
      value_template: "{% set particulates = value_json['StatusSNS']['TuyaSNS'].Illuminance %}{% if particulates > 0 and particulates <10000 %} {{particulates}} {%else%} {{0 | float}} {%endif%}"
      unit_of_measurement: "ug/m3"

Still, it would be good to have a MQTT-related solution too.

[barbudor]

Sensor values are normally sent through the SENSOR message at Teleperiod
The shortest Teleperiod is 10 seconds and can be adjusted by the Teleperiod command
There is no way Tasmota is sending sensor values every second to MQTT unless you made some rules for that

How did you get Tasmota to send Sensors every seconds ? This is what you should fix 1st

The HTTP API (that is not really RESTfull by the way) should be used lightly
Tasmota is designed for MQTT interaction

[sfromis]

Tasmota simply has no "Rest API", where did you see that?

While there exists a very rudimentary support for using HTTP to send a command, that does not make it some sort of API following RESTful principles, like using PUT for updates. Anyway, using HTTP is slower and less reliable, and Tasmota is not at all optimized for this, like it cannot reliably support requests happening to arrive at the same time. Again not at all RESTful.

[FrenkK]

@sfromis: I will correct myself: It seems that Tasmota has no REST API, you can only talk to it as if it had one. This is an important distinction.

[FrenkK]

@barbudor, sure, I will try to reproduce and send a log when I have a moment.

[sfromis]

No, you cannot talk to Tasmota as if it had a REST API, as it does not support "representational state transfer". It only supports commands.

[FrenkK]

Unmarked this thread as an answer, there is no solution in it.

[loca5790]

Having the same issue here using a drop in ESP32-C3 chip (btw looks like some data was backwards from what was on the site) but this thing is updating every second. I'm seeing sensor readings and I'm watching my RF power transmitter to confirm that it is legitimately updating once a second. I am about to force a deep sleep by wiring some additional stuff in the housing. This is too many updates and unnecessary.

Did you figure anything out?

[loca5790]

Ah!! I seee, clever. Do you have example of how you setup your API?

[FrenkK]

Ah!! I seee, clever. Do you have example of how you setup your API?

See the HA config in my reply from 14th February. No need to additionally configure Tasmota in any way.

[bam80]

Having the same issue here using a drop in ESP32-C3 chip (btw looks like some data was backwards from what was on the site) but this thing is updating every second.

Same thing happened to me yesterday on the same chip, with BLE sensor - at some point the MQTT SENSOR messages started to publish every second.
I don't know what provoked and eventually fixed it, I tried many things but nothing helped. At some point I re-enabled BLE/MQTT or such things, and then it came back to normal (with teleperiod of 300sec).

Need to keep eyes on this, will inform if it happens again.

[bam80]

at some point the MQTT SENSOR messages started to publish every second.

One thing comes to mind - could Tasmota cache the data from BLE sensor while MQTT broker was inaccessible, and then publish it all in a bunch?

[sfromis]

No. But as no one has documented what happens, the situation is unclear.

[barbudor]

If I read back the whole topic, I can't see any logs from Tasmota where I could witness the behavior.
So impossible to understand what we should look for in the code.

[loca5790]

Great thank you! I will have to remove the c3 from the board and flash later, wish it was more straightforward or I hadn't swapped them all yet.... shoot that means I have to remove them from a few devices

[loca5790]

@barbudor maybe I'm just naive can I use the GUI to flash the zip or one of the binary files instead of serial connection?

[sfromis]

You should indeed be able to upgrade to tasmota32c3.bin from the unpacked zip, like any other non-wired upgrade.

[FrenkK]

Thank you, I will try it out :)

[barbudor]

It is now merged so part of standard

[loca5790]

03:30:25.632 MQT: tele/tasmota_4E6B88/SENSOR = {"Time":"2022-03-25T03:30:25","TuyaSNS":{"Temperature":27.4,"Humidity":38.6,"TVOC":27,"eCO2":825},"TempUnit":"C"}
03:30:28.139 TuyaSNS: no immediate
03:30:28.187 TuyaSNS: no immediate
03:30:32.955 TuyaSNS: no immediate
03:30:37.165 TuyaSNS: no immediate
03:30:37.214 TuyaSNS: no immediate
03:30:42.971 TuyaSNS: no immediate
03:30:42.974 TuyaSNS: no immediate
03:30:46.225 TuyaSNS: no immediate
03:30:46.228 TuyaSNS: no immediate
03:30:50.238 CMD: SetOption136 1
03:30:50.242 MQT: stat/tasmota_4E6B88/RESULT = {"SetOption136":"ON"}
03:30:52.996 TuyaSNS: no immediate
03:30:52.000 TuyaSNS: no immediate
03:30:55.265 TuyaSNS: no immediate
03:30:55.270 TuyaSNS: no immediate
03:31:03.022 TuyaSNS: no immediate
03:31:03.025 TuyaSNS: no immediate
03:31:04.271 TuyaSNS: no immediate
03:31:04.275 TuyaSNS: no immediate
03:31:13.049 TuyaSNS: no immediate
03:31:13.052 TuyaSNS: no immediate
03:31:13.250 TuyaSNS: no immediate
03:31:13.299 TuyaSNS: no immediate
03:31:22.319 TuyaSNS: no immediate
03:31:22.323 TuyaSNS: no immediate
03:31:23.075 TuyaSNS: no immediate
03:31:23.078 TuyaSNS: no immediate

Appears to be working thank yoU!

[barbudor]

Stupid me to leave a debug log!
I'll fix the PR before it is merged

[barbudor]

@FrenkK @loca5790
I found out that TempSet (fnId 72), HumSet (fnId 74) and Timer1..2 (fnId 81..84) are not sensor measurments but settings from the TuyaMCU and should always be publish immediately whatever is SO136
So I just pushed a new PR #15231
My tests looks ok, but will be good to have you testing it once merged and built.
Thanks

[loca5790]

@FrenkK @loca5790 I found out that TempSet (fnId 72), HumSet (fnId 74) and Timer1..2 (fnId 81..84) are not sensor measurments but settings from the TuyaMCU and should always be publish immediately whatever is SO136 So I just pushed a new PR #15231 My tests looks ok, but will be good to have you testing it once merged and built. Thanks

sorry for the late response, if it's pushed Ill try it out for sure!

[barbudor]

Hi @loca5790
Never too late :)
it's in the code now, including in release 11.1.0

[loca5790]

I updated it's working.... it wiped my config and I had to restore it... although I went back and looked and looks like updates stopped about 3 hours ago, maybe coincidental.

Anything specific you want checked.

[barbudor]

Don't have any idea why your settings would have been wiped.
What do you mean by "updates stopped about 3 hours ago" ?
The SetOption136 featuer should remove all TuyaSNS measurment publication. Should only remains value changed on the device itself like target temperature on the thermostat (TempSet)

[loca5790]

Don't have any idea why your settings would have been wiped. What do you mean by "updates stopped about 3 hours ago" ? The SetOption136 featuer should remove all TuyaSNS measurment publication. Should only remains value changed on the device itself like target temperature on the thermostat (TempSet)

Simply mean I'm looking back at my recorded history from HA and the values stopped updating about 3 hours previously. When I say updates stopped.... strange thing is I think the settings got wiped when I unplugged the device and plugged it into a new power source... working fine now.

TuyaSNS only comes up under /SENSOR=

LOG:
02:48:26.681 MQT: tele/tasmota_4BEA60/STATE = {"Time":"2022-04-18T02:48:26","Uptime":"0T21:25:09","UptimeSec":77109,"Heap":196,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":3,"Objects":40},"POWER":"OFF","Wifi":{}}
02:48:26.688 MQT: tele/tasmota_4BEA60/SENSOR = {"Time":"2022-04-18T02:48:26","TuyaSNS":{"Temperature":28.4,"Humidity":34.6,"TVOC":2,"eCO2":361},"TempUnit":"C"}