29 917
modifications
Modifications
Sauter à la navigation
Sauter à la recherche
Ligne 1 :
Ligne 1 : − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
aucun résumé de modification
{{Rasp-Node-Red-NAV}}
{{Rasp-Node-Red-NAV}}
Voici une petite vue des noeuds déjà disponibles dans l'installation de base.
Voici une petite vue des nœuds déjà disponibles dans l'installation de base.
[[Fichier:Rasp-Node-Red-Basic-Nodes-00.jpg]]
[[Fichier:Rasp-Node-Red-Basic-Nodes-00.jpg]]
= Les noeuds Input =
Il y a 7 noeuds d'entrée de base dans l'installation par défaut. Ces noeuds couvrent les mécanismes de communication de base utilisé principalement par les applications IoT. Cela s'étale des protocoles Internet fondamentaux tels que UDP et TCP jusqu'à un niveau plus élevé tels que HTTP et les mécanismes MQTT de publication/souscription (''publish/subscribe'').
{| class="wikitable" border="1"
|-
| align="center" | Nom de Noeud
| align="center" | Description
|- style="font-size: 90%"
| align="left" | xx
| align="left" | yyyy
|- style="font-size: 90%"
| align="left" | inject
| align="left" | Injects a timestamp or user-configured text into a message. Can be configured to inject manually, at a set interval, or at specific times (using Cron).
|- style="font-size: 90%"
| align="left" | catch
| align="left" | Catches errors thrown by nodes on the same tab. If a node throws an error whilst handling a message, the flow will typically halt. This node can be used to catch those errors returning a message with an error property detailing the error and the source node and type.
|- style="font-size: 90%"
| align="left" | mqtt
| align="left" | Subscribes to an MQTT broker and listens on a topic, returns any data published on the topic as a new message. Supports Quality of Service levels and last data retention.
|- style="font-size: 90%"
| align="left" | http
| align="left" | Receives HTTP requests, allowing Node-RED to act as a basic web server. HTTP body is delivered as an output message along with any response. Message can contain standard URL-encoded data or JSON.
|- style="font-size: 90%"
| align="left" | websocket
| align="left" | Provides an endpoint for a browser to establish a websocket connection with Node-RED. Offers a duplex connection for browser/server combinations.
|- style="font-size: 90%"
| align="left" | tcp
| align="left" | Used to accept incoming TCP requests on a specified port or to connect to a remote TCP port. Generates messages containing the TCP data as a single – or stream of – buffer, string or base64 encoded.
|- style="font-size: 90%"
| align="left" | udp
| align="left" | Used to accept incoming UDP packets (or multicast packets) on a specified port. Generates messages containing the UDP data as a BUFFER, string or base64 encoded string.
|- style="font-size: 90%"
| align="left" | serial in
| align="left" | Reads from a serial port on the local device. Can be configured to read buffers, a specific time period or wait for line breaks.
|}
{{Rasp-Node-Red-TRAILER}}
{{Rasp-Node-Red-TRAILER}}