First a big thank you to all involved in 1.1.0. Looks fantastic and what a great choice of features. My concern is with low level efficient modules that interface with real-time hardware on Pi4 and Pi Zero via GPIO, I2C and SPI using user-space privileged access. Working backwards from the lates…

[image] ozpos: I am trying to contribute by starting off with a working copy of the NR repo If you want to create a node-red node you don't need to build node-red itself. Start here Creating Nodes : Node-RED Perhaps I have misunderstood exactly what you want to do though.

I now have a working fork of master within my IDE is that not a good starting point ? My approach is designed to be a minimum burden on the community. The plan is to see if I can single step into a working node and then create my own from an existing MCP23017 and try to detach it from I2c calls as…

[image] ozpos: I now have a working clone of master within my IDE is that not a good starting point I don't believe it is necessary to clone node-red in order to step debug a contrib node. Not sure if it ultimately matters. This is how I step debug my contrib nodes in VSCode - it might help?…

[image] ozpos: I now have a working clone of master within my IDE is that not a good starting point ? A clone of what exactly? I haven't been following every single reply in this thread - there are now 92 posts. Scanning back through, I can't see you mention which git repo you are cloning - m…

I forked master and cloned that. Now I can mess around as much as I like and revert the mess ups. It may not be necessary but it is done. I feel comfortable with JetBrains it has git built in. I can now keep in sync with master. Hey there could well be another version by the time I have got a har…

[image] ozpos: I have asked that question where it shoul be ! The #creating-nodes category.

Regarding SPI I’ve been using this excellent library and it works great within node on a pi: [image] spi-device SPI serial bus access with Node.js It’s very easy to integrate in Node-RED by either writing a node or using it within node-red-contrib-unsafe-functi…

Thank you that looks good. The problem is maintenance. If it is not part of node-red distribution it will die by not keeping up with node version changes. I propose a small collection of hardware nodes that expose a chips functions but communicates via MQ (as others have described). It may have …

[image] ozpos: it will die by not keeping up with node version changes One of the most important reasons why I think it should be kept totally separated from NR development & distribution, such "strong bindings" should be totally avoided. Instead such devices should be either INTEGRATED via a…

[image] krambriw: One of the most important reasons why I think it should be kept totally separated from NR development & distribution, such "strong bindings" The specification of a chip is static and will never change without a part number change which does not happen anywhere near as often …

Node-RED

Node-RED Forum

Improved hardware support

Hardware

knolleary 8 July 2020 21:58 95

The #creating-nodes category.

Topic		Replies	Views
Rpi5 16GB, PiOS/Debian 13 (Trixie), NodeRED 4.1.1, GPIO, i2c ... any appetite? Hardware	17	744	8 January 2026
New to Node Red - trying to decide which route? General	41	2159	2 June 2020
Node-red-contrib-i2c fails to install General	81	9290	16 August 2020
I/O switching performance on a Raspberry Pi 4 General	38	2808	14 August 2020
Need some opinion on smart home creation Dashboard	46	1592	30 December 2020

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Improved hardware support

Related topics