I guessed this might be due to addressing, so i added an additional INA219 sensor as a standalone to the I2C pins on the HAT and addressed it to 0x45, and then amended the fixed addresses in ina.html and ina219.js to reflect addresses 40, 41, 42 & 45. (as noted here: https://github.com/easybotics/node-red-contrib-easybotics-ina219/issues/15)
After that I can configure the nodes and all 4 INA219 nodes in nodered are reading values from the 4x sensors, but i continue to see the same error repeating in the console:
0.01
false
initing!
(It's a bit annoying as I want to use the system console log to record system operation, and the rolling log is swamped with the error)
If I delete the nodes in the flow, the fault persists, until i remove the node from the palette.
versions are:
Node-RED version: v2.1.4
Node.js version: v14.18.2
Linux 5.10.63-v7+ arm LE (Pi zero 2 W on buster)
npm 6.14.15,
node-red-contrib-easybotics-ina219 is as installed from the node red palatte (with only the address changes noted above different)
I've attached the flow in question and the two modified files.
Has anybody got any ideas? Have i missed anything obvious?
I have one of these: https://thepihut.com/products/power-monitoring-hat-for-raspberry-pi (https://github.com/sbcshop/Power-Monitor-HAT) Standard addresses are 0x40, 0x41, 0x42 on this board. I see this in the node red system console:
I guessed this might be due to addressing, so i added an additional INA219 sensor as a standalone to the I2C pins on the HAT and addressed it to 0x45, and then amended the fixed addresses in ina.html and ina219.js to reflect addresses 40, 41, 42 & 45. (as noted here: https://github.com/easybotics/node-red-contrib-easybotics-ina219/issues/15) After that I can configure the nodes and all 4 INA219 nodes in nodered are reading values from the 4x sensors, but i continue to see the same error repeating in the console: 0.01 false initing!
(It's a bit annoying as I want to use the system console log to record system operation, and the rolling log is swamped with the error) If I delete the nodes in the flow, the fault persists, until i remove the node from the palette.
versions are: Node-RED version: v2.1.4 Node.js version: v14.18.2 Linux 5.10.63-v7+ arm LE (Pi zero 2 W on buster) npm 6.14.15,
node-red-contrib-easybotics-ina219 is as installed from the node red palatte (with only the address changes noted above different)
I've attached the flow in question and the two modified files. Has anybody got any ideas? Have i missed anything obvious?
flows.zip ina219.zip