haspmota.parse(<json>) looks not consider "page" attribute

[ScanLabs]

Hello folk,

working on tasmota 14.5.0.2 LVGL
On Berry console trying to practice with dynamic haspmota configuration

when I issue a command like:
haspmota.parse("{\ "page\ ":10,\ "id\ ":5,\ "obj\ ":\ "label\ ",\ "text\ ":\ "100%\ "}")
note - because of web-post editor issue you see \ " ( on the berry script the space is not there )

the object is created on page 1 rather than on page 10

print(p10b5.text)
BRY: Exception> 'syntax_error' - input:2: 'p10b5' undeclared (first use in this function)

while

print(p1b5.text)
100%

Of course, creating a "pages.jsonl" with only on line like the following works fine
{"page":10,"id":5,"obj":"label","text":"100%"}

My suspect is haspmota.parse() is not well managing the "page" attribute OR I'm doing something wrong.

Any Idea to share ?

Paolo

print(p1b5.text)

[s-hadinger]

Short answer:
Use print(global.p10b5.text) and there will not be any problem anymore

Longer answer:
The problem is that when the Berry compiles print(p10b5.text) the object is not yet created and the compiler does not know that it will exist at runtime.

The safest way is to prefix with global.

[sfromis]

It does not seem to work when prefixing with global.

import haspmota
haspmota.parse('{"page":10,"id":5,"obj":"label","text":"100%"}')
print(global.p10b5.text)
BRY: Exception> 'attribute_error' - 'nil' value has no attribute 'text'
print(global.p1b5.text)
100%

Indeed, the new object appeared on page 1, not page 10.

[s-hadinger]

It is fixed now

[ScanLabs]

Thanks guys,

I was adding my notes when I saw sfromis message.

s-hadinger is this your commit ?
b29ef3d

Tnx

[s-hadinger]

Yes

[ScanLabs]

Hello s-hadinger,

simply upgraded full libesp32_lvgl on 14.5.0.2 LVGL with the last you commit .
Standard haspmota pages.jsonl looks to be not loaded any longer - or let's say, after the patch my dashboard does not appear.
Swapping back to the original 14.5.0.0 libesp32_lvgl , the display is back working.
Could your change have had an impact on the "pages.jsonl" structure ?
As usual the page-ID is set only at the beginning of the file - not repeated for each object
eg.

{"page":0,"comment":"---------- Version 2.0 ----------"}
{"id":0,"text_color":"#ffffff"}
{"id":239,"obj":"btn","x":70,"y":95,"w":180,"h":50,"bg_color":"#4f4f4f","text_color":"#44FFFF","radius":10,"text_font":"montserrat-20","text":"","border_width":2,"border_side":15,"border_color":"#44FFFF","border_opa":0,"text_opa":0,"bg_opa":0}
......
{"page":1,"comment":"---------- Page 1 Obj ----------"}
{"id":0,"bg_color":"#ad631f","text_color":"white"}
.....

Paolo

[s-hadinger]

Testing on my side, I see nothing wrong.

The problem is that your button is set to transparent because of "border_opa":0,"text_opa":0,"bg_opa":0

If you use the following it works fine:

{"page":0,"comment":"---------- Version 2.0 ----------"}
{"id":0,"text_color":"#ffffff"}
{"id":239,"obj":"btn","x":70,"y":95,"w":180,"h":50,"bg_color":"#4f4f4f","text_color":"#44FFFF","radius":10,"text_font":"montserrat-20","text":"","border_width":2,"border_side":15,"border_color":"#44FFFF","border_opa":255,"text_opa":255,"bg_opa":255}

{"page":1,"comment":"---------- Page 1 Obj ----------"}
{"id":0,"bg_color":"#ad631f","text_color":"white"}

[ScanLabs]

Hey s-hadinger,

that was only an example how the page attribute is used on my project. My pages.jsonl file is 30KB with a lot of other objects and 7 pages
OK let me try to debug and understand why it is not working at my side.
I will report any news.

Tnx for the quick reply.

Paolo

[s-hadinger]

Yes please. I ran my huge demo template with no problem.
Use seriallog 4 to see all the details of HASPMOTA parsing

[ScanLabs]

1st test : I used the latest tasmota32-lvgl.bin deployed .

tasmota32-lvgl.bin | http://ota.tasmota.com/tasmota32/tasmota32-lvgl.bin | 2528k | 20250511 11:19

with this bin, everything works as expected - I can confirm the fix .
NOTE: I have not changed a bit of my pages.jsonl

Instead of spending time understanding why new libesp32_lvgl seems struggling to work on my built based on 14.5.0.2 LVGL, I will migrate my personal built to the latest 14.6.0.2 and let you know if there's any combination of extra defines I used that is affecting the behavior.

Tnx