How to display on Tasmota ESP32 GUI an own variable parameters - simple example ?

[ON-state]

Hi,

I am trying to do first steps in Berry and I would like to begin with easy step.

My idea is to display on ESP32 WROOM (let's called it as hub) a parameters from another ESP32 sensor using websend or BLE.
I tried to display temp, humididy, pressure on Counters but I can't change the name and counters are not except float value.

I tried to play with web_sensor() and tasmota.web_send() but no effect.

[sfromis]

To put data on the Tasmota web UI front page via Berry, one approach is to create a driver in Berry. Here's an example of a driver:
https://tasmota.github.io/docs/Berry-Cookbook/#creating-an-i2c-driver

You can skip the parts about I2C usage, the key part is the callback for web_sensor using tasmota.web_send_decimal with a formatted message including labels and values. And adding it as a driver using tasmota.add_driver. The callback will be invoked every couple of seconds when the front page is viewed in a browser.

[ON-state]

tasmota.add_driver this was missing. Thank you

[ON-state]

I decided to keep the questions in the same thread due to my project. Becuse I see there is lot of question how to read the var,mem in Berry and display on GUI I will keep everything there.

I set the communication between ESP32's (slave and master) with Websend:

Rule1 AM2301#Temperature DO var1 %value% .... Websend [192.xxx.xxx.xxx] Mem1 %var1% ENDON

ESP32 working in DeepSleepTime 3600 (1 hour)

Then I read the Mem1 parameter on other ESP32 like this:

var list

 def read()
         var var1 = tasmota.cmd('Mem1')['Mem1']
         .....
         self.list = [int(var1), ............]
         return self.list
 end

 def every_second()
      self.read()
 end

Then I display the parameters on GUI using def web_sensor()

I know it is not a high fly method but tying the best what I can do.

As you see I'm shaing the every_second() as my interval reader. But in my case to often for my every 1 hour transmiter. Can I override any other function to perform it only once for ex. during opening the GUI ?

Temporary I found this:

def set_timer_modulo(delay,f,id)
  var now=tasmota.millis()
  tasmota.set_timer((now+delay/4+delay)/delay*delay-now, def() set_timer_modulo(delay,f,id) f() end, id)
end

[sfromis]

Rule1 AM2301#Temperature DO var1 %value% .... Websend [192.xxx.xxx.xxx] Mem1 %var1% ENDON

That does not work well, as %var1% will be expanded before the whole rule starts. This shorter way works better:

Rule1 AM2301#Temperature DO Websend [192.xxx.xxx.xxx] Mem1 %value% ENDON

However, I'd recommend against using Mem1 that way, as every update causes a flash write, to the detriment of flash chip lifetime. Better use Var1 unless you nave a strong reason to want the value to be persistent across boots.

In this case, I'd still see it as a better strategy to create a command using Berry, to avoid all that faff about going via rule variables. Then you could directly update your Berry list as data arrives, instead of having every_second to do idle work.

BTW. I'd generally suggest to avoid mixing rules and Berry features on the same device, but of course that's not a "hard rule".

While set_timer_modulo can work well for a repeated "ticker", using the cron feature is a lot more flexible.

[ON-state]

BTW. I'd generally suggest to avoid mixing rules and Berry features on the same device, but of course that's not a "hard rule".

Maybe my descriotion was not clear enough.

Diagram:

I was trying to play with cron but looks like I don't undestand the coding rules. Becuse all time I got f parameter first time.

BRY: failed to load '/myDisplay.be' (syntax_error - /myDisplay.be:7: 'f' undeclared (first use in this function))

I was trying to launch the cron in init() function:

def init()
   tasmota.add_cron("*/5 * * * * *", f, "every_5_s")
 end

 def f()
  self.read_mem()
 end

That is why I think over againt and decided to display read the var's only once during opening the WEB UI but I see close loop of read_mem() function in console:

13:04:48.329 RSL: RESULT = {"Var10":"21.5"}
13:04:48.342 RSL: RESULT = {"Var11":"68.6"}
13:04:48.354 RSL: RESULT = {"Var12":"1020.3"}
13:04:48.367 RSL: RESULT = {"Var14":""}
13:04:48.379 RSL: RESULT = {"Var15":""}
13:04:51.292 RSL: RESULT = {"Var10":"21.5"}
13:04:51.305 RSL: RESULT = {"Var11":"68.6"}
13:04:51.318 RSL: RESULT = {"Var12":"1020.3"}
13:04:51.332 RSL: RESULT = {"Var14":""}
13:04:51.345 RSL: RESULT = {"Var15":""}
13:04:54.265 RSL: RESULT = {"Var10":"21.5"}
13:04:54.278 RSL: RESULT = {"Var11":"68.6"}
13:04:54.291 RSL: RESULT = {"Var12":"1020.3"}
13:04:54.305 RSL: RESULT = {"Var14":""}
13:04:54.318 RSL: RESULT = {"Var15":""}

Class:

class MYDISPLAY

var list

 def init()
 
 end

 def read_mem()
 
  var var1 = tasmota.cmd('Var10')['Var10']
  var var2 = tasmota.cmd('Var11')['Var11']
  var var3 = tasmota.cmd('Var12')['Var12']
  var var4 = tasmota.cmd('Var14')['Var14']
  var var5 = tasmota.cmd('Var15')['Var15']

  self.list = [int(var1), int(var2), int(var3), int(var4), int(var5)]

  return self.list

 end

  def web_sensor()
  
    import string

    self.read_mem()

       var msg0 = string.format(
             "{s}Alias{m}%s {e}"..
             "{s}BMP280 Temperature{m}%.1f C{e}"..
             "{s}BMP280 Humidity{m}%.1f %%{e}"..
             "{s}BMP280 Pressure{m}%.1f hPa{e}",
             "OUTSIDE", self.list[0], self.list[1], self.list[2])
        tasmota.web_send_decimal(msg0)

        var msg1 = string.format(
             "{s}Alias{m}%s {e}"..
             "{s}BMP280 Temperature{m}%.1f C{e}"..
             "{s}BMP280 Humidity{m}%.1f %%{e}",
             "ATTIC", self.list[3], self.list[4])
        tasmota.web_send_decimal(msg1)

        var msg2 = string.format(
             "{s}Alias{m}%s {e}"..
             "{s}SR04 Distance{m}%.1f cm{e}"..
             "{s}Tank Fill{m}%.1f %%{e}",
             "TANK", self.list[3], self.list[4])
        tasmota.web_send_decimal(msg2)
  end

end

mydisplay = MYDISPLAY()
tasmota.add_driver(mydisplay)

[sfromis]

web_sensor is called for every front page refresh, default at intervals of 2.345 seconds. That's not really a "close loop", but only what you asked for 😉

Still, I'd suggest avoiding all that faffing around with rules vars, when you can get values into Berry much more directly.

The reason for

BRY: failed to load '/myDisplay.be' (syntax_error - /myDisplay.be:7: 'f' undeclared (first use in this function))

is that the function f must be defined before being used, due to Berry using a single-pass compiler not doing lookforward to later code.

[ON-state]

Still, I'd suggest avoiding all that faffing around with rules vars, when you can get values into Berry much more directly.

sfromis, can you share some link to example or materials regarding communication Berry-to-Berry of 2x ESP32 ?

[sfromis]

Such an extremely open-ended question would take a lot of material to cover, and depends very much on your preferences for how to do things, of which you did not show much.

Using MQTT, a very rudimentary approach could be to publish a Br command to execute a bit of Berry code on the other end, like
mqtt.publish('cmnd/otherdevice/Br', 'mydisplay.outsidetemp=5 mydisplay.outsidehum=90 mydisplay.outsidepress=1010')
This relies on you having those instance variables in the class.
Not the greatest strategy in a larger scenario, but could be a POC starting point.