Plua - QuickApp development

[jgab 2,644]

Yes, 

specifically, the Lua vm is embedded via a Python library (Lupa), and because it brings in the standard Lua vm (there are many choices) as a binary, it links with it's standard C libraries like normal (ex. C string functions). 
However, a standard Lua interpreter seems to pick up the LC_CTYPE when running and setting that for the C library. The Lupa embedding didn't, and it wasn't documented what I could see

Edited April 23 by jgab

[Łukasz997 117]

This really is impressive work. What stands out to me is not only the amount of code, but - maybe mainly - the fact that project appears as structured, intentional.

Edited April 23 by Łukasz997

[jgab 2,644]

6 minutes ago, Łukasz997 said:

This really is impressive work. What stands out to me is not only the amount of code, but - maybe mainly - the fact that project appears as structured, intentional.

Well, it's my 4th attempt to create a HC3 emulator / developer tool... 

[jgab 2,644]

v1.3.2 released - lots of potential bugs squashed...

New library, speed.lua that can be used in the emulator to run code faster than realtime.

Please login or register to see this code.

It intercepts setTimeout and setInterval and the various debug functions so it runs everything as fast as possible ,just bumps the virtual time logged.
We need to call fibaro.speedTime(hours, fun) on the main function that drives our timers.
The --%%time directive allow us to start the emulator at a given date (works without the speedTime function)

Really handy when debugging schedulers over weeks or months...

[Christb 33]

On 4/24/2026 at 1:12 PM, jgab said:

v1.3.2 released - lots of potential bugs squashed.

When I do >pip install plua -u, I am getting v1.3.11, not 3.1.2, Normal?

[jgab 2,644]

1 hour ago, Christb said:

When I do >pip install plua -u, I am getting v1.3.11, not 3.1.2, Normal?

Yes, made a couple of releases since 1.3.2…

[Christb 33]

With the last version, I have now the following errors during the QA process in vscode:

[06.06.2026][07:02:07][INFO   ][PLUA]: Starting helper server on 192.168.1.32 8082
Fibaro SDK, online, (0.7281s)
[06.06.2026][07:02:07][DEBUG  ][HOMETABLE5555]: ---- onInit() starts ----
[06.06.2026][07:02:07][DEBUG  ][HOMETABLE5555]: QA HomeTable id:5555 starts
[06.06.2026][07:02:07][DEBUG  ][HOMETABLE5555]: --------- onInit( ends --------)
[06.06.2026][07:02:08][DEBUG  ][HOMETABLE5555]: ======================== update of HomeTable starts ========================
[06.06.2026][07:02:08][DEBUG  ][HOMETABLE5555]: -------- Getting Device list --------
[06.06.2026][07:02:11][DEBUG  ][HOMETABLE5555]: #devListAll 409
[06.06.2026][07:02:11][DEBUG  ][HOMETABLE5555]: #devListVisible 409
[06.06.2026][07:02:11][DEBUG  ][HOMETABLE5555]: #aQ less VoipUsers= 404
[06.06.2026][07:02:49][DEBUG  ][HOMETABLE5555]: 156 Escalier_Grenier . Lum_Escalier_Grenier_ = 195
[06.06.2026][07:02:49][DEBUG  ][HOMETABLE5555]: HomeTable[ Escalier_Grenier ][ Lum_Escalier_Grenier_ ] id= 195
WARNING:plua.fastapi_process:\U0001f527 QuickApp 5555 not found
[06.06.2026][07:03:09][DEBUG  ][HOMETABLE5555]: 248 Communs . Lum_Communs = 324
[06.06.2026][07:03:09][DEBUG  ][HOMETABLE5555]: HomeTable[ Communs ][ Lum_Communs ] id= 324
[06.06.2026][07:03:11][DEBUG  ][HOMETABLE5555]: 253 Grenier_Pignon . Lum_Pignon_Grenier = 329
[06.06.2026][07:03:11][DEBUG  ][HOMETABLE5555]: HomeTable[ Grenier_Pignon ][ Lum_Pignon_Grenier ] id= 329
WARNING:plua.fastapi_process:\U0001f527 QuickApp 5555 not found

 

But at the end of the QA process, the HomeTable is correctly created and also displayed in the webUI as a table.

 

 

What can create such Warning message?

[jgab 2,644]

Well, your QA seems to do some heavy processing (home table with 409 devices?) initially which keeps it busy.
The web frontend meanwhile tries to call the Lua engine (your QA) to get the UI to display. It doesn't get it and logs the warning. It will retry and eventually it succeeds and everything should work. So it's harmless. Maybe the warning message could be more informative.
(This has always been an issue if the lua engine is too busy to answer the frontend...)