Connection nodes speak of listener and sender, and of send_queue_size
mqtt and http take websocket's vocabulary: their Mode is LISTENER/SENDER, default names read mqtt_listener_… and http_listener_…, and mqtt's publish_queue_size is send_queue_size. No alias stays behind, so the flow store rewrites the old setting in every published and draft mqtt node when it opens, in the same migration as trigger → debounce. Every mqtt and http setting carries a one-line description for the editor, and the node-types reference uses one wording for direction and says that an http sender publishes a JSON object response on its outputs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
@@ -86,10 +86,10 @@ Publish the change. The Function now responds to sensor readings instead of
|
||||
the test value. If your sensor sends a JSON object such as
|
||||
`{"temperature": 18.0}`, set `json_key` to `temperature`.
|
||||
|
||||
An MQTT node with input ports publishes to its configured topic; one with
|
||||
output ports subscribes. Add a publishing node only after checking the payload
|
||||
format your device expects. A relay may need `ON` and `OFF` rather than a
|
||||
boolean.
|
||||
An MQTT node with inputs is a sender and publishes to its configured topic;
|
||||
one with outputs only is a listener and subscribes. Add a sender only after
|
||||
checking the payload format your device expects. A relay may need `ON` and
|
||||
`OFF` rather than a boolean.
|
||||
|
||||
!!! tip "Keep the first test on screen"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user