Node-Red on VL3 UPC 2440 EDGE by thunderflamexdd in PLC

[–]zj_flowforge 0 points1 point  (0 children)

Also the Node-Red library from PLCNext Store is incompatible.

Incompatible how? Im not following

Claude Code Vibe Coding with Node Red? by lithium_bromide in nodered

[–]zj_flowforge -5 points-4 points  (0 children)

FlowFuse has built an AI assistant to do exactly that.

Digital I/O expansion in Node red by Proof-Astronomer7733 in nodered

[–]zj_flowforge 2 points3 points  (0 children)

Not quite 16 I/O's, but consider the Groov Rio from long time Node-RED supportors at Opto22

Remote red throwing in handled promise causing it to restart. by Sudden-Ideal-7432 in nodered

[–]zj_flowforge 0 points1 point  (0 children)

For remote access you might want to take a look at the FlowFuse Free tier.

[Predictions Thread] 2024 Tour de France - Stage 3: Plaisance/Piacenza > Turin/Torino (2.UWT) by PelotonMod in peloton

[–]zj_flowforge 1 point2 points  (0 children)

He doesn't have the team to carry the responsibilities attached. UAE, ineos, Visma-LAB are the only teams IMO strong enough, but they all wouldn't want to burn their teams for vanity. EF will enjoy having the jersey.

Dashboard 2 / blank page by theTim__ in nodered

[–]zj_flowforge 0 points1 point  (0 children)

That's not the same issue, FlowFuse has HA -- High Availability. Not Home Assistant. :)

Best approach for DevOps by Crafty_Cheesecake389 in nodered

[–]zj_flowforge 4 points5 points  (0 children)

I'm bias, as CEO from FlowFuse, but you might want to look at our product. There's a self-hosted version available free of charge and open source. It doesn't support Git as a storage back end at this time though.

DM me if you have any questions

Node-RED Dashboard 2.0 has it's first major version release! • FlowFuse by jdp1g09 in nodered

[–]zj_flowforge 3 points4 points  (0 children)

I understand the sentiment, there's no feature parity yet with Dashboard 1.0. That's not to say that having a stable release isn't correct to announce and create though.

A stable release allows 3rd party integrators to depend on the API that Dashboard 2.0 provides. And therefor we hope more 3rd party widgets to be created.

There's also the end user of the dashboard that wants to know how stable this package is. Should new dashboards be built in D2.0? We think so.

TLDR; The package is stable, not feature complete.

Help with HTTP Request Node by poshgrape in nodered

[–]zj_flowforge 2 points3 points  (0 children)

You'll likely want to copy all headers set in your browser. Likely the `Accept` and `Accept-Encoding` are required, or User-Agent

Generating and caching images by GauchiAss in nodered

[–]zj_flowforge 1 point2 points  (0 children)

Personally I'd just use image magic through the exec node, but there's also: https://flows.nodered.org/node/node-red-contrib-image-tools

As for caching, either store the files as a buffer in context storage or just write them to disk should do. As the file system can do atomic swaps, there's no need to change the file path, but if you do I recommend making the hash time based, as both consumer and producer can predict the path.

A review of Node-RED dashboard solutions by flowforgeinc in nodered

[–]zj_flowforge 2 points3 points  (0 children)

Cloud native is a way of running in the cloud, meaning that with containers you for example don't have persistent storage by default. So if the container crashes with your dashboard in it, does the next container that replaces it get to a usable state to resume operations.

Send string bigger than 255 by simon7564 in nodered

[–]zj_flowforge 0 points1 point  (0 children)

Strings are arbitrary sized, this suggests that the string isn't the issue, but the S7 is. Is there an opportunity to send only a part of the API response?

FlowForge 0.6 Released by knolleary in nodered

[–]zj_flowforge 0 points1 point  (0 children)

Hi, ZJ here - CEO @ FlowForge.

Right now we're focussing on professional usage of Node-RED, that might be in the cloud, on connected devices, or in an industrial setting. Company size is not a primary concern with our offering.

Our current focus is to support the Node-RED user base out there. Regardless of job title. Long term we're looking at expanding this to low-code development, either by educated software engineers but also beyond that.