thanks for your reply. i have several devices. some invoke via http, some invoke via mqtt, others invoke via websocket. but my main server only handle http. so i setup adge serve to convert http, mqtt, websocket to http.
sorry to confuse, and very appreciated your direction.
In fact, thinking about it, that is effectively what I already do. Most sensors provide their data via MQTT already, but for those that don't, modbus devices for example, I poll them and write the values to MQTT so anywhere they are needed they are available via MQTT.
get your points. in coming may not from devices only. so there are difference types of incoming protocal. what confuse me is what node websocket in do? i am assuming, it triggered when devices provide data, but in fact it triggered when websocket serve response to devices.
then boot a websocket serve. the green mark of websocket in node and debug print show it connected.then i connected websocket and send a msg to the serve via websocket testing tool.
the flow stay idle no any response while websocket testing tool connected the serve.
The websocket-in node is used for establishing the websocket client connection.
Once connected, you can send data to the websocket-out node (if setup properly it is "internally" connected to the websocket-in node - this is required to understand which connected client is sending/receiving data).
So in your example flow - the http request node is only called once.