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 read Offline updates somewhere on the internet, not sure where though.
I took info from here https://community.victronenergy.com/articles/38710/victron-raspi-hat.html?childToView=71020#comment-71020
And info from here https://community.victronenergy.com/questions/19608/raspberry-pi-analog-inputs-tank-input.html
Can you explain or give a link to the more info for the driver please so I may find the file and perhaps edit it to include a name feature.
Many thanks
hi, I don't know about how you-the-community :-) made temp sensing work on a rpi, nor what driver that uses, sorry. But I'm sure others here can help; or maybe self-help by just reading and trying a lot more.
The other thing you could try, just to make sure, is install a more recent image, yesterday I released v2.70~2-large-image-8.
I'm getting nowhere fast at the moment so I'd appreciate a pointer or two.
I've reinstalled v2.60-image-large-7 on my RPi 3 B+ and it runs OK.
I've downloaded this swu (it does say it's for an RPi 4 though). Should I be able to update from this file from a USB stick and if so how as I can't?
It will update from USB to v2.60~38-large-image-6 but no further
Thank you for any help
Hi, If you have an rpi3; you’ll need to use rpi3 files.
Which means my previous advise put you in the wrong direction, as there are no recent large-image files for an rpi3 yet. Sorry.
So, to see if that fixes it, you’ll have to wait I’m afraid.
maybe there is another way to fix your original problem (unable to use the temp sensor in node-red on a venus-large install);
maybe someone else has ideas on how to do that / work around it.
Ps as far as I know, verification errors when writing sdcards can only mean one thing: broken sd card.
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.
Hey both, normally its this one:
https://github.com/victronenergy/dbus-adc
But, for the rpi + temp sensor, I have no clue how thats done.
If you look at the commit logs of above, you can see a "add custom name support" commit early last year, iirc.
Success!
typing dbus-spy into terminal gives this output:
Services
com.victronenergy.digitalinput.input01 Bilge pump
com.victronenergy.digitalinput.input02 Bilge pump
com.victronenergy.fronius
com.victronenergy.logger
com.victronenergy.modbusclient.tcp
com.victronenergy.modbustcp
com.victronenergy.qwacs
com.victronenergy.settings
com.victronenergy.system
com.victronenergy.tank.builtin_adc2_di2 Generic Tank Input
com.victronenergy.tank.builtin_adc4_di0 Generic Tank Input
com.victronenergy.tank.builtin_adc6_di1 Generic Tank Input
com.victronenergy.temperature.builtin_adc3_di1 Generic Temperature Input
com.victronenergy.temperature.builtin_adc5_di0 Generic Temperature Input
dbus -y com.victronenergy.system / GetValue
'AvailableTemperatureServices': {'com.victronenergy.temperature/23/Temperature': 'Battery temperature sensor (1)',
'com.victronenergy.temperature/24/Temperature': 'Battery temperature sensor (2)',
'default': 'Automatic',
'nosensor': 'No sensor'},
Does this mean anything to you? I'm not that familiar with dbus, yet!
scroll down and select one of the temperature sensors. You will then get data like this..
Key data is do you have the CustomeName. The fields Mgmt/ProcessName is the name of the process that is driving the sensor and Mgmt/ProcessVersion is the software version. Need to compare this against the git repository to confirm if you have a bug or just outdated software.
Installed dbus-adc 1.27 from here:
https://github.com/victronenergy/dbus-adc/releases
I have run dbus-spy again but it still displays 1.17 !
Well, I found this which shows how to upgrade:
But it doesn't run the dbus now. The dbus-adc.conf was empty so I filled it in as per the example. There is mention of read_adc.sh but that makes no difference.
Is it time to give up on this and buy a Cerbo and add Node-Red to it?
Node-Red is available in a test image for the Cerbo, I have it running at the moment.
Did you reboot between installed of the dbus-adc.
Have you looked in the dbus-adc logs to see if there is anything that will give you some pointers?
cat /var/log/dbus-adc/current | tai64nlocal
