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)
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
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
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 Thinger.io!