# data[].attributes.body
Notizen 25.05.

Screencast Durchführung

Handout schriftlicher Screencast

Prozessdokumentation Abschlussphase

Dinge, die wir gelernt haben, Reflexion in Abschlussphase Prozessdokumentation, inhaltliche Verbesserungen (wie ist die Installation gelaufen zB, sool ist, probleme, gut gelaufen, alle das Projekt von Julian zeigen lassen, Prozessdokumentationsübergreifend

Starten mit dem Gantt Diagramm

Agenda in Präsentation einfügen

Dienstag 31.05.22 23:59 Uhr

Meilensteinplan anschauen

Abweichungen/Reflexion: Projektstrukturplan und Gantt 3 Mal komplett überarbeitet, Alle können Programm bedienen, Installation frühzeitig anstoßen

Abschätzung Zeitmanagement

# data[].attributes.body
-    Für Installation von Programmen zukünftig mehr Zeit nehmen

-          Informationen über Prozess-orientierte Arbeitsschritte vor der Bearbeitung dieser klar machen (PSP & Gantt Diagramm mehrfach erneuern hat viel Zeit gekostet)

-          Bedienung des Programms sollte jeder beherrschen

# data[].attributes.body
Screencast Skript

Hallo und herzlich Willkommen zu diesem Screencast über NodeRed. Wir sind Rico Hendricks, Lisa Over, Mohammad Yousuf Rezai, und Julian Kröll, und gemeinsam haben wir uns damit befasst, Wetterdaten mit dem Flow basierten Editor NodeRed abzurufen, und in einem Dashboard darzustellen. -- Rico

Die Oberfläche ist in 4 Teile geteilt: Die Menüleiste, die Palette mit Nodes, der Flow Bereich, und die Seitenleiste mit Informationen. Nodes sind die Codebestandteile, welche wir nutzen, um gewisse Funktionen auszuführen oder umzuleiten: Hier sieht man Beispielweise eine Switch Node, welche je nach Eingabewert eine andere Ausgabe zur Folge hat. Sie ist somit mit dem Switch oder Case in anderen Programmiersprachen vergleichbar. -- Julian

Diese Nodes werden miteinander verbunden, sodass Daten Schritt für Schritt verarbeitet werden können. Dank der grafischen Benutzeroberfläche sind die Verbindungen zwischen den einzelnen Programmierbausteinen klar und übersichtlich dargestellt.

Reichen einem die verfügbaren Nodes nicht aus, so hat NodeRed die "Function" Node, welche erlaubt die eingegebene Message mit JavaScript anzusprechen und zu verarbeiten. Darüberhinaus können neben den Standard Nodes auch noch einige aus einer Bibliothek importiert werden! -- Yousuf

So haben wir mit dem importierten Modul node-red-contrib-dwd-local-weather lokale Wetterdaten abgerufen, und dann mit dem Rest des Flows weiterverarbeitet. Das Endresultat: Ein Dashboard, in welchem man verschiedenste Wetterdaten einsehen kann.

Hier haben wir in Klartext den Ort, die Luftfeuchtigkeit, die Frostgefahr, die Temperatur- und Windkategorie, sowie in Grafen sowohl die Temperatur als auch die Windgeschwindigkeit. Dank diesem Dashboard sind alle Werte auf einen Blick einsehbar. Wenn gewünscht, können dank dem Modul auch noch weitere Wetterdaten hinzugefügt, ersetzt oder entfernt werden. -- Lisa

Und das wars! Vielen Dank für ihre Aufmerksamkeit, und noch einen schönen Tag. -- Rico

# data[].attributes.body
Luftdruck und Luftfeuchtigkeit muss angepasst werden bzw. Nodes entsprechend konfiguriert werden

# data[].attributes.attachment_link.title
Wetter und Klima - Deutscher Wetterdienst - Glossar - B - Beaufort-Skala

# data[].attributes.attachment_link.description
Das Wetter- und Klimalexikon des DWD erläutert die wichtigsten meteorologischen und klimatologischen Begriffe und wird ständig ausgebaut.

# data[].attributes.attachment_link.readable_text
Das Wetter- und Klimalexikon des DWD erläutert die wichtigsten meteorologischen und klimatologischen Begriffe und wird ständig ausgebaut.

Frost

Zoom

Von Frost bzw. Luftfrost spricht man, wenn die Lufttemperatur (im Regelfall gemessen in 2 m Höhe über dem Boden) unter den Gefrierpunkt des Wassers (0 °C) abgesunken ist.

Es gibt nachfolgende Formulierungen und Einteilungen:

Begriff

Temperaturspanne

leichter Frost

< 0 °C bis einschließlich -5 °C

mäßiger Frost

unter -5 °C bis einschließlich -10 °C

strenger / starker Frost

unter -10 °C bis einschließlich -15 °C

sehr strenger / sehr starker Frost

unter -15 °C

Siehe hierzu:

Leistungen zum Thema:

# data[].attributes.attachment_link.title
Wetter und Klima - Deutscher Wetterdienst - Glossar - F - Frost

# data[].attributes.attachment_link.description
Das Wetter- und Klimalexikon des DWD erläutert die wichtigsten meteorologischen und klimatologischen Begriffe und wird ständig ausgebaut. Von Frost bzw. Luftfrost spricht man, wenn die Lufttemperatur (im Regelfall gemessen in 2 m Höhe über dem Boden) unter den Gefrierpunkt des Wassers (0 °C) abgesunken ist.

# data[].attributes.body
https://www.youtube.com/watch?v=X8ustpkAJ-U

# data[].attributes.body
https://flows.nodered.org/node/node-red-dashboard

# data[].attributes.attachment_link.readable_text
A set of dashboard nodes for Node-RED

This module provides a set of nodes in Node-RED to quickly create a live data dashboard.

These nodes require node.js version 8. The last version to support node v6 was 2.9.5.

From version 2.10.0 you can create and install widget nodes like other Node-RED nodes. See the Wiki for more information.

For the latest updates see the CHANGELOG.md

Pre-requisites

The Node-RED-Dashboard requires Node-RED to be installed.

Install

To install the stable version use the Menu - Manage palette option and search for node-red-dashboard, or run the following command in your Node-RED user directory - typically ~/.node-red:

npm i node-red-dashboard

Restart your Node-RED instance and you should have UI nodes available in the palette and a new dashboard tab in the right side panel. The UI interface is available at http://localhost:1880/ui (if the default settings are used).

If you want to try the latest version from github, you can install it by

npm i node-red/node-red-dashboard

Settings

The default url for the dashboard is based off your existing Node-RED httpRoot path with /ui added. This can be changed in your Node-RED settings.js file - ui: { path: "ui" },

You can also add your own express middleware to handle requests by using the ui: { middleware: your_function } property in settings.js. For example

ui: { path: 'ui', middleware: function (req, res, next) { // Do something more interesting here. console.log('LOGGED') next() } },

You can also set the dashboard to be read only by ui: { readOnly: true }. This does not stop the user interacting with the dashboard but does ignore all updates coming from the dashboard.

Layout

The dashboard layout should be considered as a grid.

Each group element has a width - by default 6 'units' (a unit is 48px wide by default with a 6px gap).

Each widget in the group also has a width - by default, 'auto' which means it will fill the width of the group it is in, but you can set it to a fixed number of units.

The layout algorithm of the dashboard always tries to place items as high and to the left as they can within their container - this applies to how groups are positioned on the page, as well as how widgets are positioned in a group.

Given a group with width 6, if you add six widgets, each with a width of 2, then they will be laid out in two rows - three widgets in each.

If you add two groups of width 6, as long as your browser window is wide enough, they will sit alongside each other. If you shrink the browser, at some point the second group will shift to be below the first, in a column.

It is advisable to use multiple groups if possible, rather than one big group, so that the page can dynamically resize on smaller screens.

Features

The widget layout is managed by a dashboard tab in the sidebar of the Node-RED editor.

Layout

Tabs - From here you can re-order the tabs, groups and widgets, and add and edit their properties. You can also open the layout tools that may help you organise the widgets more easily than via the sidebar.

Links - to other web pages can also be added to the menu. They can optionally be opened in an iframe - if allowed by the target page.

Site

Title - the title of the UI page can be set.

Options - optionally hide the title bar, and allow swiping sideways between tabs on a touch screen. You can also set whether the template uses the selected theme or uses the underlying Angular Material theme. You can also choose to use the Angular Material theme everywhere.

Date Format - sets the default date format for chart and other labels.

Sizes - sets the basic geometry of the grid layout in pixels. The width and height of widgets can be set, as can the width of groups. These are the basic definitions of the "units' used elsewhere within the dashboard.

Theme

Style - the theme and font of the UI is set in the dashboard sidebar. You can select a default Light, Dark or Custom Theme. You cannot have different themes for each tab.

You can also choose to use the basic Angular Material themes instead if you like, either just within any ui_templates or for the whole Dashboard. This will only affect angular components so some of the charts and so on may need extra work.

Note: For users creating their own templates the following CSS variable names are available to help pick up the theme colours.

--nr-dashboard-pageBackgroundColor

--nr-dashboard-pageTitlebarBackgroundColor

--nr-dashboard-pageSidebarBackgroundColor

--nr-dashboard-groupBackgroundColor

--nr-dashboard-groupTextColor

--nr-dashboard-groupBorderColor

--nr-dashboard-widgetColor

--nr-dashboard-widgetTextColor

--nr-dashboard-widgetBgndColor

Don't forget there are also extra ui widgets available on the Node-RED flows website. Search for node-ui- or contrib-ui- .

Group labels are optional.

Most widgets can have a label and value - both of these can be specified by properties of the incoming msg if required, and modified by angular filters. For example the label can be set to {{msg.topic}}, or the value could be set to {{value | number:1}}% to round the value to one decimal place and append a % sign.

Each node may parse the msg.payload to make it suitable for display. This converted version is exposed as the variable called value, (see example above).

Any widget can be disabled by passing in a msg.enabled property set to false;. Note: this doesn't stop the widget receiving messages but does stop inputs being active and does re-style the widget.

Most ui widgets can also be configured by using a msg.ui_control message - see config-fields.md for futher details.

Audio out - a widget that will let you play audio (wav or mp3) or send Text to Speech (TTS) to the client.

Button - the icon can be set using either Material or fa-icons - the colour and background colour may also be set. If the widget is sized to 1 wide the icon has precedence.

Chart - has both line, bar and pie chart modes. Also the X-Axis labels can be customised using a date formatter string. See this document for more information on the chart data formats accepted.

Colour Picker - a colour picker widget.

Date Picker - a date picker widget. The displayed Date format can be specified in the Site tab using moment.js formatting.

Dropdown - a dropdown select widget has been added. Multiple label, value pairs can be specified. The choices can also be set via msg.options containing an array of objects. If just text then the value will be the same as the label, otherwise you can specify both by using an object of "label":"value" pairs :

[ "Choice 1", "Choice 2", {"Choice 3": 3} ]

Setting msg.payload will pre-select the value in the dropdown.

Form - a widget that can be composed of several sub-widgets. When submitted all values are submitted as a single message.

Gauge - has 4 modes - standard (simple gauge), donut (complete 360°), compass, and wave. You can also specify the colour range of the standard and donut gauges.

Notification - creates alerts to the user - can either be a toast popup, or a dismissable alert box. The alert may be targeted to a single user.

Numeric - a Numeric input widget with up/down buttons.

Slider - a simple horizontal slider, with variable step size.

Switch - can also set two icons and/or colours depending on state.

Template - the template node allows the user to specify and create their own widgets within the framework using HTML, Javascript. This is an Angular.js widget. You may also use this to override the built in CSS styles.

Text - A read only widget, the layout of the label, and value can be configured.

Text input - text input box, with optional label, can also support password, email and colour modes.

UI-Control - allows some dynamic control of the dashboard. Sending a msg.payload of the tab number (from 0) or tab_name will switch to that tab. Tabs can be enabled/disabled/hide/show via msg like {"tabs":{"hide":["tab_name_with_underscores"],"show":["another_tab_name"],"disable":["unused_tab_name"]}}. Groups can be hidden and made visible via a msg like{"group":{"hide":["tab_name_group_name_with_underscores"],"show":["tab_name_another_group"],"focus":true}}. Outputs a msg.payload for every browser connect and loss, and every tab change. This can be used to trigger other actions like resetting the visibility of tabs and groups.

Tip: The Text widget will accept html - so you can use it together with the fa-icons we already use to create indicator type widgets.

Icons

The dashboard has 4 sets of icons built in. They are

And one that can only be used if you have a permanent connection to the internet

Again note you have to add iconify- to the icon name in the icon set of your choice. You may also optionally specify a size in standard px or em notation. Default is 24px. You must also add a ui_template node that loads the necessary iconify library into the header of the dashboard. It should contain

You may also create your own set of icons using Icofont. Once downloaded you can serve them locally via Node-RED and add them to the head of the dashboard page by using a ui_template node : e.g.

then you can use then as per above by adding the icofont- prefix e.g. icofont-badge

Or just use them in a template

And finally via an image - https://{myserver/path/image.png}

You can use them in any of the Icon fields. You may also be able to use some of them for example in labels via their inline style eg <i class="fa fa-flag"></i>

Due to the size of the dashboard libraries it can take a long time to load if you are running on wireless network. It is possible add a custom loading page if you wish. To do so add a file called loading.html to the node_modules/node-red-dashboard/dist/ folder. A simple example could be

Securing the Dashboard

You can use the httpNodeAuth property in your Node-RED settings.js file to secure the Dashboard as it is created the same way as other HTTP nodes are. The details can be found at the bottom of this page in the docs http://nodered.org/docs/security

Multiple Users

This Dashboard does NOT support multiple individual users. It is a view of the status of the underlying Node-RED flow, which itself is single user. If the state of the flow changes then all clients will get notified of that change.

Messages coming from the dashboard do have a msg.socketid, and updates like change of tab, notifications, and audio alerts will be directed only to that session. Delete the msg.sessionid to send to all sessions.

Discussions and suggestions

Use the Node-RED Discourse Forum: https://discourse.nodered.org/c/dashboard or the Dashboard-ui channel in Slack to ask questions or to discuss new features.

The current work in progress list is shown in the Github Project.

Contributing

Before raising a pull-request, please read our contributing guide.

This project adheres to the Contributor Covenant 1.4. By participating, you are expected to uphold this code. Please report unacceptable behavior to any of the project's core team.

Developers

cd ~\.node-red\node_modules git clone https://github.com/node-red/node-red-dashboard.git cd node-red-dashboard npm install

The plugin uses the dist folder if it exists. Make sure it has been deleted if you want to use the non-minified version while developing. After finishing changes to the front-end code in the src folder, you can use gulp to update and rebuild the minified files and update the appcache manifest.

We also have suggested lint and js styles that can be checked with:

gulp lint gulp jscs

If submitting a Pull Request (PR) please do NOT include the minified /dist files.

Thank you.

# data[].attributes.attachment_link.description
A set of dashboard nodes for Node-RED This module provides a set of nodes in Node-RED to quickly create a live data dashboard. These nodes require node.js version 8. The last version to support node v6 was 2.9.5. From version 2.10.0 you can create and install widget nodes like other Node-RED nodes.

# data[].attributes.body
benötigt Bilder aus d. Screencast

# data[].attributes.body
Kann in Node-Red importiert werden
Gibt bisher nur Temperaturen aus

# data[].attributes.body
Falls wir Infos daraus brauchen

# data[].attributes.body
Für die Einstellungen der Node

# data[].attributes.attachment_link.readable_text
Node Red node to retrieve local weather forecast from DWD (Germany)

A node red node that returns German DWD MOSMIX current / forecasted weather for a given location.

It gives you the following data:

Temperature in °C (in a 2 m height)

Relative humidity in %

Windspeed in m/s (in a 10 m height)

Wind direction in degrees

Rain probability in %

Expected rain amount (precipitation) for the next 24 hours in kg/m²

Timestamp of the forecast

Fig. 1: Node appearance

Remark: This node is mainly useful if you are interested in weather data for Germany. International weather data is available for only a couple of european locations (see MOSMIX stations below). Examples for international locations are Bergen, London, Dublin, Brussels, Luzern, Lille, Locarno, Le Mans, Madrid, Ibiza, Klagenfurt (and many others).

The weather data is provided by DWD (Deutscher Wetterdienst, Frankfurter Straße 135, 63067 Offenbach).

References:

Installation

In Node-RED (preferred)

Via Manage Palette -> Search for "node-red-contrib-dwd-local-weather"

In a shell

go to the Node-RED installation folder, e.g.: ~/.node-red

run npm install node-red-contrib-dwd-local-weather

Usage

The easiest usage of the node is using internal triggering:

BasicUsageFlow.json

Fig. 2: Basic node usage

In this example the node cyclically reads out the DWD data and emits it as an output msg.

Node Configuration

Fig. 3: Node properties

Node configuration is quite simple. Only setting the property MOSMIX Station to select the required weather forecast location is mandatory.

MOSMIX station

Set this property to select the weather forecast location.
The format is a 5 character id. Allowed ids are given in the stations catalog (in CFG file format) of the DWD (german weather service): See coloumn 'id' and search for your location.

Examples:

id = 10389 for Berlin, Alexanderplatz

id = K1174 for Heinsberg (NRW)

id = K4476 for Tirschenreuth (BY)

Look ahead Hours

Hours to look ahead into the future. Use 0 to get actual weather.

When you set Look ahead hours, the weather data returned will be for x hours in the future. If you look at the temperature for 12 hours ahead for example, you should see a different number returned unless that temperature happens to be exactly the same to the actual temperature.

Note: This configuration property is superseeded by an input msg with a msg.payload.lookAheadHours element (see secion Input below).

Omit message on start

For compatibility with the openweathermap node, this node emits a message with current weather data immediately once the flow is deployed. If this is not desirable, it can be deactivated here. In any case, the node will emit a message after the repeat cycle in case this is set (see below) or once it is triggered by receiving a message.

Repeat

Automatic cyclic repeat (in seconds). If set to a value > 0, the node automatically repeats the DWD data query and emits a msg telegram at its output.

Hint: Do not set this value too small to avoid unneccesary traffic. Appropriate repeat intervals are several minutes due to the weather data does not change at a higher rate than 15-20 seconds, typically one minute.

Additional fields

Basics

With the Additional fields property you can add further weather data to msg.payload.
Possible elements can be selected from this MOSMIX element list from the DWD.
Several elements can be selected and have to be comma-separated.

Output modifiers

The data provided by DWD is on an hourly basis. By default, output values will be linearly interpolated. Some data fields such as "SunD" (Yesterdays total sunshine duration) in the below example are only provided once every X hours or even once per day and interpolation does not make sense. With modifiers you can change how the output value is calculated in those cases. When not specifying a modifier, the value for those fields will be 'NaN' in most cases.

Output modifiers are added as a prefix to the field name. So instead of just using "SunD", you would use ">SunD" to return today's predicted total sunshine duration.

Available modifiers:

< go back in time to find the last value for this field

> go ahead in time to find the next value for this field

° assume the field value is a temperature and convert it from Kelvin to Celsius

See also: Node issue "NaN error with precipitation 24h and 3h".

Example

The following figure shows the msg.payload structure of an example with "FF,FX1,>SunD,SunD1,R101,°Td,VV,W1W2,wwTd":

Fig. 4: Additional fields example msg.payload contents

MOSMIX elements used by the node

The following MOSMIX elements are used as the basis for the node's msg.payload values:

payload.tempc: "TTT"

payload.humidity: "Td" and "TTT"

payload.windspeed: "FF"

payload.winddirection: "DD"

payload.precipitation_perc: "wwP"

payload.precipitationNext24h: "RR1c"

Name

A name for the wheather location may be set via this property.

Topic

Allows to configure the topic for emitted messages.

Input

The node is triggered by any input msg with arbitrary contents.

If the input msg contains the element msg.payload.lookAheadHours its value superseeds the Look ahead Hours node configuration property.

Outputs

The node emits a msg whenever it is triggered by an input msg or at the configured Repeat interval (see node configuration above).

The default msg attributes are:

payload.station - Description (location) of the station

payload.tempc - Temperature in °C

payload.humidity - Relative humidity

payload.windspeed - Windspeed in m/s

payload.winddirection - Winddirection in °

payload.precipitation_perc - probability of rain in per cent (so a value of 4 means 4%)

payload.precipitationNext24h - total precipitation in the next 24 hours in kg/m2

payload.forecast_dt - epoch timestamp of the forecast

payload.precipitation% - DEPRECATED, same as payload.precipitation_perc

In case of a value set to the node configuration property Topic the output msg contains an additional attribute msg.topic with the set content in addition to the msg.payload object.
As an example, if the node configuration property Topic is set to "myTopic" the output msg looks like this:

Fig. 5: Example output msg with topic configuration property set to "myTopic"

Examples

Remark: Example flows are present in the examples subdirectory. In Node-RED they can be imported via the import function and then selecting Examples in the vertical tab menue.

Basic example

This example shows how to trigger the node and how to evaluate the msg.payload.tempc element.

BasicExampleFlow.json

Fig. 6: Basic example flow

Click to expand code snippet of the flow

[{"id":"c9a4786f.ee8328","type":"inject","z":"c1f84551.fa0b5","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"str","x":210,"y":1320,"wires":[["63c7e662.9ec0c8"]]},{"id":"63c7e662.9ec0c8","type":"dwdweather","z":"c1f84551.fa0b5","name":"Berlin, Alex","mosmixStation":"10389","lookAheadHours":"0","additionalFields":"","repeat":"0","x":390,"y":1320,"wires":[["52b1bc57.f3fe74","7a6b8898.d8d578"]]},{"id":"52b1bc57.f3fe74","type":"debug","z":"c1f84551.fa0b5","name":"Temperatur in °C","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.tempc","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":610,"y":1320,"wires":[]},{"id":"7a6b8898.d8d578","type":"debug","z":"c1f84551.fa0b5","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":570,"y":1280,"wires":[]}]

Example using Additional fields

The configuration of the property Additional fields was set to "FX1,SunD1,VV". Therefore the elements msg.payload.FX1 (max. wind gust in the lasts hour), msg.payload.SunD1 (sunshine duration in the last hour) and msg.payload.VV (visibility) appear additionally at the output.

AdditionalFieldsExampleFlow.json
Fig. 7: Example with Additional fields flow

Click to expand code snippet of the flow

[{"id":"6b9dad75.8e1cfc","type":"dwdweather","z":"c1f84551.fa0b5","name":"Berlin, Alex","mosmixStation":"10389","lookAheadHours":"0","additionalFields":"FX1,SunD1,VV","repeat":"0","x":390,"y":1680,"wires":[["98ed4e40.07d5","e5ef0089.cf48","69ba80bb.54cfc","36980239.12325e","b21cfb33.0eb55","47c88c29.1cea44","5a984276.9804c4"]]},{"id":"9e5e1177.58e82","type":"inject","z":"c1f84551.fa0b5","name":"","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"str","x":190,"y":1680,"wires":[["6b9dad75.8e1cfc"]]},{"id":"98ed4e40.07d5","type":"debug","z":"c1f84551.fa0b5","name":"windspeed in m/s","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.windspeed","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":730,"y":1800,"wires":[]},{"id":"e5ef0089.cf48","type":"debug","z":"c1f84551.fa0b5","name":"wind direction in °","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.winddirection","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":740,"y":1860,"wires":[]},{"id":"69ba80bb.54cfc","type":"debug","z":"c1f84551.fa0b5","name":"max. wind gust last hour","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.FX1","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":760,"y":1920,"wires":[]},{"id":"47c88c29.1cea44","type":"debug","z":"c1f84551.fa0b5","name":"sunshine duration last hour in seconds","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.SunD1","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":810,"y":1980,"wires":[]},{"id":"b21cfb33.0eb55","type":"debug","z":"c1f84551.fa0b5","name":"rel. humidity in %","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.humidity","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":730,"y":1740,"wires":[]},{"id":"36980239.12325e","type":"debug","z":"c1f84551.fa0b5","name":"temperature in °C","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.tempc","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":740,"y":1680,"wires":[]},{"id":"5a984276.9804c4","type":"debug","z":"c1f84551.fa0b5","name":"visibility in m","active":true,"tosidebar":false,"console":false,"tostatus":true,"complete":"payload.VV","targetType":"msg","statusVal":"payload.windspeed","statusType":"auto","x":720,"y":2040,"wires":[]}]

Note that often the values have to be scaled to have more 'handy' values.

License

Apache 2.0 (c) Christian Stein

# data[].attributes.attachment_link.description
Node Red node to retrieve local weather forecast from DWD (Germany) A node red node that returns German DWD MOSMIX current / forecasted weather for a given location.

# data[].attributes.body
kann man sich angucken

# data[].attributes.body
Kann man importieren

# data[].attributes.body
Zum Erstellen

# data[].attributes.attachment_link.title
Wetterdaten in Node-RED abrufen | ElektrikTrick