Node red not running in Venus OS v3.80~11 available for public testing

Beta testing Venus OS beta testing
54

On your lan, yes.
Vrm is for remote access.

55

image
image1186Ɨ323 28.8 KB

And rolled back to 3.72 I can open node red the proxy and lan way.

56

For me: what comes with OS-Large, plus:

  • @mschaeffler/node-red-format
  • node-red-contrib-average
  • node-red-contrib-buffer-parser
  • node-red-contrib-os
  • node-red-contrib-ui-led
    But there were no new Nodes installed since 3.6x.

And Iā€™m accessing it direct, locally in LAN.
It does NOT happen when I deploy changed Nodes or Flows. Just when I do a full deploy.
But itā€™s a minor thing anyway, at least for me. I just noted it.

57

Hi Nick. Yes. I installed nodes for Suncron and Shelly and have removed all non-victron now. Does not make a difference.

So safe mode all good. All tabs/flows disabled and NodeRed back to enabled also all good. But as soon as I enable the first tab it crashes again. Please note that my first tab is basically just a bunch read nodes to set global variables for use on other (still disabled) tabs. I have the dashboard installed but I donā€™t use it.

In short: have not been able to come up with anything useful :slight_smile:

58

Indeed. This is caused by a bug that got introduced via node-red-contrib-victron-1.7.7 (in 3.80~10). Iā€™ve just put 1.7.8 on the list for the next beta that fixes the ā€œTypeError: Cannot read properties of null (reading ā€˜toStringā€™)ā€ bug.

As far as I could determine only systems that have flows that carry a node that reads from the com.victronenergy.settings service where affected.

1 Like
59

Disabled all nodes that read from the ā€¦settings service and enabled everything else. It no longer crashes. Will wait for the next beta and confirm.

60

It is now available in 3.80~14.

2 Likes
61

Iā€™m back in business!

3 Likes
62

8 posts were split to a new topic: Nodered nodes appear in grey colour not blue or orange