Adding %json% variable for rules

[anishsane]

Consider a case of IR-receive.

The output is of the form:

{"IrReceived":{"Protocol":"NEC","Bits":32,"Data":"0x02FD40BF","DataLSB":"0x40BF02FD","Repeat":0}}

If we want to send this to a logging server, we can use an mqtt broker.
Or we have to use rules snippets to concatenate the string, something like:

on IrReceived#Protocol do var1 %value% endon on IrReceived#data do var2 %value% endon on IrReceived#datalsb do var3 %value% endon on IrReceived#bits do var4 %value% endon on IrReceived do webquery http://logger.local/irreecived/%var1%/%var2%/%var3%/%var4% GET endon 

Instead, it would be easier if we could use

on IrReceived do webquery http://logger.local/irreecived POST %json% endon 

Of course, MQTT server is an option, but it is an overhead if your use case is limited.

(I tried searching if this suggestion is already covered, but did not find any.)

[barbudor]

Http is an overhead

If you are using an ESP32, you can do that in Berry

[anishsane]

Sorry, I think I have used the wrong words and unnecessarily abstracted the things.

Let me explain the actual setup.

• I have a Raspberry Pi zero running a Python server to serve an AC remote control webpage over HTTP. We can use it to control the AC from the phone's browser.

• The actual IRsend operation is done by a Tasmota device with esp8266 that is controlled by the RPI over http://tasmota-ip/cm?cmnd=...

• I am also using IRRecv to update the Python server state in case we use the physical remote control to control the AC. That way, the browser based software remote is in sync with the updates from the physical remote.

• In that case, I want to send the IR receive data from Tasmota to the Python server via HTTP. Hence this proposal:

    on IrReceived#Protocol=daikin216 do webquery http://rpi.python.ip/irreecived POST %json% endon 
  

I am currently running a MQTT server that Tasmota pushes the IRrecv data to and then a monitor application that watches (subscribes) for these data updates on the MQTT server and updates the python server state.

[barbudor]

That was a cheap one : #20718
Wait for acceptance by Theo and merge

[anishsane]

Thank you so much!

[barbudor]

@anishsane Don't throw your MQTT broker to quickly
This change is not safe and make Tasmota crash as soon as the JSON is more than 10-15 characters
So definitively not a good solution

I have asked Theo to revert that change.
We will need more time to think is something more memory efficient is possible

[anishsane]

Hmm.
If it is a hardware limitation (due to memory size) we have to revert it.
Thanks for the efforts though!