This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.
Using Node-Red v2.6-large-image-7 on a RPi3 B+ with an mcp3208 ADC.
When I try to use the Temperature Sensor node I'm unable to select either sensor.
I get this message in the "Edit Temperature Sensor node" box:
Multiple temperature sensors were found with the same name. You can set a custom name for the device in Venus settings.
I am unable to see how to change the name of the sensor, any help would be much appreciated.
Moved to Modifications Space for non-Victron-supported systems/questions and to bring the question into the attention of other users of non-supported systems. Cheers!
Hi,
On your Venus device:
go to Device List --> Temperature sensor you want to rename --> Device --> Name
You can enter a name for the sensor there.
BR
Using Node-Red v2.6-large-image-7 on a RPi3 B+ with an mcp3208 ADC.
I see there is a version that says it's for a rpi4
https://www.dropbox.com/sh/i8ru22o4ydws1rx/AADpa8lj5s2APZ2JS78OGPjKa?dl=0
I do not see Offline updates only Online updates.
From within the software I see this but get an error.
> Not seeing Offline updates
where did you see that exact wording?
You do see it, 'install firmware from SD/USB', but is just named differently.
> Temp sensor
What software are you running to read out that MCP? You must have done some modifications, as I’m quite sure Venus OS doesnt read that out of the box?
My guess is that driver is missing the feature to set a name to the temp sensor.
hope that helps you & the rest of people here to get it solved, all the best
I still have not been able to get the Name option to display.
In an attempt to learn more I have taken a look at the gui folder files. The file PageDeviceInfo.qml has a section MbEditBox, id I remove the line show: item.valid with // the Name option is displayed. I can type in a name but it is not saved. Does this mean anything?
MbEditBox {
id: name
description: qsTr("Name")
item.bind: Utils.path(root.bindPrefix, "/CustomName")
//show: item.valid
maximumLength: 32
enableSpaceBar: true
}
I notice in this file there are a couple of other instances of "show: item.valid", they also don't appear.
It may well be that dBus does not hold the data and have a valid path. Use the dBus-spy tool to look at the temperature sensor and see if it has that data element associated with it.
the QML was not displaying it as item.valid must have been false, that means the data element dose not exist.
If dBus-spy shows it not there, then I suspect the driver which is maintaining the dbus path has not created it, if you can let me know the driver I’ll dig through the source and see if I can find the issue.
