Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node-red-raspberry #2

Open
masalinas opened this issue Jun 24, 2016 · 7 comments
Open

node-red-raspberry #2

masalinas opened this issue Jun 24, 2016 · 7 comments

Comments

@masalinas
Copy link
Owner

masalinas commented Jun 24, 2016

picapp - apple macbook air 1

@RAMI40

This comment has been minimized.

@masalinas
Copy link
Owner Author

masalinas commented May 15, 2020

When you installed all related dependencies in nodeRED could you see all new nodes included in the johnny package for example in the side menu of nodeRED??

@RAMI40

This comment has been minimized.

@masalinas
Copy link
Owner Author

You said that you don't have npm installed, in your raspberry. I recomend that you installed the last stable node version in your Raspberry SO and of course the last npm package manager first. Also use the last stable nodeRED in your project and not the default one that could be installed in the Raspberry SO.

Any way, check this link if it could help you:

Node "rpi-gpio out" doesn't do the expected in GPIO 18 (Pin 12)

@RAMI40

This comment has been minimized.

@masalinas
Copy link
Owner Author

masalinas commented May 15, 2020

Debug in nodeRED doesn't really exist.

You could trigger debug logs to the right side panel of nodeRED or use lamps in your nodes indicating the status like you know but not more.

If you need any more complicated debug in a more complicated logic in javascript or other backend language for your data received from your hardware devices I recomend implement this logic outside nodeRED using for example the IBM Loopback framework is you are using a nodeJS backend. I used it many years and is fantastic nodeJS backend framework. Thwen you could use the API services exported by this framework or others in your flows using the javascript node of nodeRED or directly the HTTP. I recomended the first option.

My 5 years experience in nodeRED tell me that not build your logic inside nodeRED only use nodeRED like a message router.

The correct flow must be: capture the outside dara inside nodeRED, transfom, persist, etc this data outside nodeRED (IBM Loopback for example) and publish the results alarms etc inside nodeRED to other UI services like Angular, React ot any client side framework that you prefered.

Good Luck in your project!

Regards

@RAMI40
Copy link

RAMI40 commented May 15, 2020

Thanks for the detailed answer.

With Debug window i meant the Panel / Window in NodeRED.

Best Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants