Can i use it to connect to Opera GX’s new smart home update?
@ATHOM @Emile I hope you support this app since you published.
Three related questions about using MQTT Server and HomeyScript together for state management.
1. Internal publish → trigger loopback
When a HomeyScript (or any flow action) publishes via the “Publish topic” action card, the “A message is published on topic” trigger card in the same app does not fire. The trigger only responds to messages from external MQTT clients (Node-RED, MQTT Explorer, ESP32, etc.). The publish action completes without error, but the trigger is silent.
This was independently confirmed by another user @robertklep . Is this by design to prevent feedback loops? Is there a setting to enable it?
2. Retained messages
Does the “Publish topic” action card support publishing with the retain flag? And if a flow subscribes to a topic that already has a retained message, does the trigger fire immediately on that retained delivery — or only on new publishes?
If both work, retained topics would be a clean way to store and share state between scripts and external tools without needing logic variables.
3. HomeyScript logic variables — single-variable read
Homey.logic.getVariables() fetches all variables every time. Is there a way to read a single variable by ID or name — something like Homey.logic.getVariable({ id }) — without pulling the full list?
The full fetch is slow (~200ms) and forces scripts to cache the object locally, which creates a stale-read race condition when two HomeyScript instances run concurrently and both overwrite shared state.
