@sjp770 Ended up being a newer version of Node-Red was required.

I2C relays are still a pain if anyone find a node based solution to those.

Node-RED is getting more popular, is there any chance you could get the Neuron devices to work DIRECTLY with Node-RED?

Take the RPI GPIO nodes in node red. Super simple to use, drop in place, specify with gpio you want to interact with. All my automation is in Node-RED, even direct hardware access to my current UniPi for the Digital inputs and the I2C bus. That said things like I2C aren't very friendly to work with. And when you get to a M303 with 34 Digital Inputs I'd have no idea where to start.

Does the Neuron still have the ability to replace the OS and run your own flavour of linux and install things like node-red though?

Thanks for that, but seeming I wont be using a EMO-R8 anything besides 0x20 in that list is ok?

I'm new to I2C but im looking to plug in a 4 channel dimmer board based on the PCF8574 chip. The addresses it can be set to are:
// Device address -> 0x27, 0x26, 0x25, 0x24, 0x23, 0x22, 0x21, 0x20
// Device address -> 0x3F, 0x3E, 0x3D, 0x3C, 0x3B, 0x3A, 0x39, 0x38

Which would work best with the UniPi?

@tomas_hora Thanks for the link but it doesn't explain why the gpio ports are unavailable when SPI is disabled. I used the raspi-config method.

@zeus I was just looking at this same issue, I think its because the GPIO's in question are tied up with SPI so dont show in Node-Red. If you find a way to get them to be visible in node-red id love to know.

I can connect to I01-I06 & I11 only on the UniPi 1.1

I am trying to get direct access to the Digital In and the relays on the UniPi through Node-red. If I run an i2c scan I can see all the devices as specified in the hardware manual. I can connect I01-I06 & I11 through the rpi-gpio nodes, but no more. Any tips for disabling SPI to free up the other gpio ports? I havn't done the cabling mod for pins 13&14 yet but plan to.

If I can interface with the hardware on the UniPi 1.1 directly I would prefer this as the only reason to use EVOK would be to get the inputs and outputs into Node-red... this would mean i'd skip all the EVOK stuff, less to reconfigure in the case of a hardware failure and less to go wrong software wise.