aedes | Barebone MQTT broker that can run on any stream server | Websocket library

Let's start by saving the difficulty setting in a variable along these :

As per the comments the docs say:

WebSockets requests are treated as long-running HTTP requests in Cloud Run. They are subject to request timeouts (currently up to 60 minutes and defaults to 5 minutes) even if your application server does not enforce any timeouts.

Accordingly, if the client keeps the connection open longer than the required timeout configured for the Cloud Run service, the client will be disconnected when the request times out.

Therefore, WebSockets clients connecting to Cloud Run should handle reconnecting to the server if the request times out or the server disconnects. You can achieve this in browser-based clients by using libraries such as reconnecting-websocket or by handling "disconnect" events if you are using the SocketIO library.

This will apply to MQTT over WebSockets so changing the timeout will allow longer connections but you should also ensure that the client is automatically reconnecting when the connection does go down.

Short answer, no.

You can only access Node-RED running on IBM Cloud via HTTP/HTTPS, you will not be able to connect to the any broker you ran in the Node-RED process externally.

This is because the Node-RED instance is behind a reverse HTTP/HTTPS proxy.

You could deploy Node-RED in a Docker container or on a Virtual machine, or just make use of an external MQTT broker. But without a much better understanding of the whole problem you are trying to solve it is impossible to be more specific.

According to ?specaccum

permutations - Number of permutations with method = "random". Usually an integer giving the number permutations, but can also be a list of control values for the permutations as returned by the function how, or a permutation matrix where each row gives the permuted indices.

The following code will take the array and convert it back to a string via a buffer.

If you want to use both MQTT over Websockets and native MQTT you will need to configure the broker to listen on 2 separate ports. You can't listen for both on the same port.

e.g. This will accept native MQTT connections on 1883 and Websocket connections on 8883

There are 2 different things here.

1. Retained messages. This is a flag set on the message by the publisher, it tells the broker to hold on to the message and always deliver the last retained message on any given topic to a client when they first subscribe to that topic before any new messages are sent. The last retained message will always be replaced by the next message published on that topic that also has the retained flag set. You can read more about retained messages here

2. Queued messages. If the client subscribes to a topic at greater than QOS 0 then the broker will queue up messages sent for that client while it is offline. The client needs to reconnect using the same client ID and with the cleanSession flag set to false. You can read more about persistent sessions and queued messages here

You have to bind the this context of the class instance to a method if you'd like to pass that method as a callback. There are a couple of ways to do this in TypeScript.

Defining the method using an arrow function:

While it might not be achieved in a formula, utilizing the Pivot Table function will result in the second table that you are looking for, as well as being dynamic.

In Google sheets, select your data range (Table 1) -> Click on the Data -> Select Pivot Table. From there confirm that the data range is correct and that New sheet is selected. Click create and you should be moved to the new sheet with the Pivot table editor pane open.

To get the desired output as Table 2 add Family to Rows and Genera to Values. By default Genera will be summarized by COUNTA; in order to get the UNIQUE Count all you need to do is change COUNTA to COUNTUNIQUE.

This Table will update automatically to any changes made within the original range, however make sure that if you add/remove any new rows that you update the Data Range within the Pivot table editor.