Hi guys.

First of all, I want to thank Xard777 for sharing his tools with us.

After several days running the homelab with the default installation and not receiving any signal besides Stay_Cash, I decided to carry out some deeper investigations that I would like to share.

HomeLAB 4.0 modelo 13" monitor Confirmed Issues In The Original Community Version

Relative vault_memory.db path

File: src__vault_memory.py
The code used db_path="vault_memory.db" directly.
This could cause HomeLAB to open or create a different database depending on the working directory.
This was one of the reasons the imported historical data was not reliably queried.
LTM / Vault search did not properly filter by symbol

File: src__orchestrator.py
query_similar() searched similar memories without properly restricting results by symbol.
This could mix USTEC, BTCUSD, US30, NASDAQ, and other instruments.
It also did not restrict results to historical events with a valid outcome.
Incorrect fallback to BTCUSD

File: src__orchestrator.py
analyst_dept() and the vault summary used BTCUSD as the default symbol.
This explains older logs where the vault was queried as BTCUSD even while the panel was running USTEC.
Fragile parser causing float('.') errors

File: src__orchestrator.py
The regex accepted only [\d.]+, which could capture . and then fail with:
could not convert string to float: '.'
This issue existed in the original Community code.
Inconsistent coil scale

File: src__orchestrator.py
The Community version mixed coil_tightness values in both 0-1 and 0-100 scales.
This affected historical matching, vault lookup, and APEX/coil interpretation.
MT5 Bridge accepted zero prices

File: src__mt5_bridge.py
parse_timeframe() accepted price=0.0.
This could contaminate M1/M15 data with zero prices, as we saw in the interface.
GUI accepted zero prices

File: src__gui.py
_update_from_snapshot() and handle_signal() updated prices even when they were 0.
This allowed the panel to display M1/M15 as zero.
Analyst prompt had no explicit structured state block

File: src__gui.py
There was no HOMELAB_STATE block.
The Analyst depended on loose text from the blackboard/snapshot, increasing the risk of stale prices or wrong symbol interpretation.
Tkinter thread error

File: src__utils.py
start_clock_thread() called clock_label.after() from a secondary thread.
This is the same pattern that caused:
RuntimeError: main thread is not in main loop

It seems that now it is working correctly, but I would like to know your opinion about this, Xard.

If you’d like, I can share my version of the Homelab for evaluation.

Best regards