Node-RED Plugin Version 1.5.0-1

Node-RED Plugin Version 1.5.0-1

Sample control panel a Node-RED integration with

From we have released a new Node-RED Plugin version with some improvements and fixes.

Between the highlights of this new version, we have added the possibility to filter by tags in the bucket read node, needed feature when using product buckets.

Bucket Read node form with bucket tags

Also available for configuration in the input message:

Bucket Read node tags property documentation

It is now possible to add a project to the device and bucket create nodes, extending and replicating the capabilities available in the UI.

Bucket Create node form with bucket tags

Between the fixes, we have made some improvements into the storage read and write nodes.

The full changelog is available here

In regards of the underlying Node-RED, we have update it to the last version 3.1.0. More information in Node-REDs blog post.

Checkout the doc for the this plugin.

This is a companion discussion topic for the original entry at

Hello, @jaimebs

  1. We need the aggregation by month to generate reports. Is it possible to implement?

  2. The ‘Bucket Reading’ node does not consider the Time Zone different from UTC 00:00.
    We need to generate reports with data that consider UTC -03:00, using the ‘spread’ function. Without the possibility of configuring UTC in the ‘Bucket Reading’ node or in the ‘node-red-contrib-thinger’ plugin, analyzes in NodeRed are generated differently than in our Dashboard (which considers UTC -03:00).

Dashboard shows the Value ‘58’ (aggregation by day) considering the Time Zone UTC -03:00

NodeRed analyzes with Time Zone UTC 00:00. Therefore, the result is ‘68’ (aggregation by day)

Visualization on the Bucket Screen, which considers UTC -03:00. Result ‘58’ (aggregation by day) is the same as seen on the Dashboard

  1. The ‘Bucket Reading’ screen does not save the “Time Period” setting when ‘months’ is selected

When trying to save the “Time Period” as “1” “months”, the setting is reset to “1” “minutes”.

Hello, @jaimebs

We report the two implementation requests and the bug described above on Github.

Without these features and corrections we are unable to generate reports using the “bucket reading” node, as we need aggregated data by month with the ‘spread’ function, considering the UTC -03:00 time zone.

Thanks for updating ‘node-red-contrib-thinger’ and implementing the ‘spread’ function

Hi @George_Santiago

They do indeed seem to be bugs. I can say that we can fix the ones regarding the bucket read node. As for the one about the timezone, the fix might come from the server rather than the plugin. However well take a look.

Thank you for the report and for opening the issues in GitHub

After installing version 1.5.1 of the plugin, I identified that the server memory went from 40% to 50%, is this increase within the expected range?

No significant changes where introduced between version 1.5.0 and 1.5.1.

We will keep an eye on this report

Our update was from 1.4.3 to version 1.5.1.
Perhaps the memory increase was due to the new version of NodeRed. But it was a significant increase.

It could be, but I wouldn’t really expect many changes in performance from the previous version of Node-RED, which was 3.0.2

We haven’t detected anything in our instances. It may be due to the operations that handle the actual upgrade if the upgrade was done just before checking the memory status. Or any other operation running in the server.

We’ve update the plugin to version 1.6.0 which tackles some of the issues reported here. Let us know if you find any issues and thanks again for the report and your continuous interest in improving! :smiley:

1 Like