Hi all,

In some branches network, where the security policy is strict (eg. only allowing http/https), running mqtt using port 8883 is not working. My options is using only port 443, but it's not working. After few dyas, i learned that we need to specified Application Layer Protocol Nego (ALPN) options in [TLS handshaking](https://aws.amazon.com/blogs/iot/mqtt-with-tls-client-authentication-on-p

Die Einstellungen für das Dashboard:

Wenn man Style Angular , dort das Dark Theme und Farben ausgewählt hat.

Geht die Einstellung nach gefühlt 24h verloren. Vermutlich bis der BrowserCache abgelaufen ist.

I tryed to start the docker on a Raspberry Pi with Raspbian Stretch/Hypriotos and run every time into strange problems with starting all dockers. A tested Raspberry Pi sample configuration with less problems would be nice.

The module "Discovery Document Loader" loads document content (the msg.payload), under an attribute named "value", when the standard expectation is to have it under the attribute named "text" in Discovery.
This requires to enrich the "value" field, generating "enriched_value" instead of "enriched_text", which is non-standard and a client application may fail if enrichments are not where expected

• The internal node-red documentation for nodes needs some love
  • Pretty up the documentation here, look at the node-red docs for formatting best practices
• Add example flows section of some simple ( hopefully common ) use cases

Currently the control-nodes and the webservice-nodes don't share the messages/status of the miniserver-config node. All in all the messaging architecture is a bit clumsy.

Maybe there should be a msg queue which delegates the messages to all existing nodes... not thought this to the end, yet.

• include uncertain flag in msgs
• add possibility to filter uncertain msgs in value and rpc event node

Ref: https://homematic-forum.de/forum/viewtopic.php?f=77&t=52762