And the 15 minute schedule fetch endpoint seems to point to the 1 hour installation stats endpoint.
@UpCycleElectric By this change, the boat page will show the speed value of the GPS with the lowest VRM device instance which reports a Fix. You can adjust the VRM device instance for any GPS via Settings > VRM > VRM Device Instance and thereby inherently select which GPS is to be used. This should make your life way easier 
Thanks Philipp, but unfortunately, it doesn’t.
When I started developing the gps speed filter I did notice the USB GPS to be assigned device instance 000 and the virtual GPS 100 and there seemed to be an issue reassigning another device instance no to the USB GPS (above that of the virtual devices).
But that doesn’t affect my filter at all because I need the USB GPS device removed from VenusOS, as a GPS device, altogether for reliable access to the underlying (USB to) serial port for reading the full NMEA GPS datastream that the GPS transmits onto it at 1 second intervals.
And I put an emphasis on ‘reliable’ here because at first it seemed possible to read from the serial port (by means of the Node-RED serial node) by just stopping the GPS device in VenusOS and preventing it to be re-added by VenusOS’s automatic device detection script and opening the serial port with the serial node, but this only provides a very erratic datastream.
Once the GPS has been detected by VenusOS (as in: assigned a device instance), the normal (VenusOS) commands to disable and remove it will not stop/prevent some background process(es) from frantically attempting to access the GPS, most likely as a part of the discovery/reconnect processing. I assume that prevents reliable access to the datastream.
The working way to reliably read the NMEA datastream from the USB GPS is by preventing the GPS to be detected by VenusOS at all. So every update/reboot it needs to be physically (a) removed from the Cerbo GX, then the VenusOS discovery script needs to be removed by means of ssh access and then, with the serial node up and running in Node-RED, the device can be re-inserted.
(a) or this has to be simulated with linux root commands to stop/delete and re-add/enable the underlying serial port itself I later discovered.
Oh and in case it isn’t obvious, with the physical GPS device effectively removed before detection by VenusOS, further detection thereof prevented and a serial port node connected to the usb-to-serial device after re-insertion, there are no issues with the virtual GPS device instance number to resolve. Because for all practical purposes the virtual GPS is the only GPS device known to exist to VenusOS.
The Devil is in the details I’d say, check our DMs for further information, it’s all there.
Phillipp, I am not sure it is working, I have set my USB GPS to instance 101 and I have a Node-RED virtual GPS instance 100. The USB GPS is erratic so Node-RED smooths the position and when the engine i s off forces the value to 0 meters per second. I am still seeing the Cerbo and VRM reporting speeds above 0 with the engine off.
Are you interested in a copy of our (in work) solution per DM?
It involves:
- Preventing the USB GPS to be added as a GPS device to/by VenusOS
- Reading the NMEA datastream directly from the USB-to-serial port
- Preprocessing the NMEA datastream to discard ‘erratic’ readings based on NMEA ‘quality of signal’ indicators
- Extracting the relevant location, direction and velocity values
- Adding motor power to the available datastream
- Applying a rudimentary ‘smartfilter’ to disregard ‘unrealistic’ acceleration datapoints
- Postfiltering for ‘stop’ (standstill) and max speed (of the boat)
- Applying a fast weighted averaging filter (exponential over a few seconds
- Linear upsampling the output from 1Hz to 5Hz
- Feeding location and velocity to the virtual GPS
Thanks for the offer Jan, your Node-RED skills are beyond mine, I stay with my simple smoothing and see about moving the receiver.
It’s not that hard. Philipp provided a valuable hack (local.rc) on how to get rid of the last true hurdle: preventing VenusOS from adding the USB GPS as gps device to VenusOS after a reboot of the Cerbo GX. Once I find the time to implement that (or the Victron devs add a raw NMEA output to the GPS node) , I’ll do a final refactor of our Node-RED flow to make it completely transparent and self explainatory. I’ll then leave it up to another coder to port that proof of concept back to the Venus OS NMEA parser.
A bit of manoeuvering right before entering the harbour. The RPM gauge displays energy use in Ah/Km so that Speed * ‘RPM’ = Amps (with a filter that is too slow and should better be synchronized to the speed filter)
PS, you wouldn’t believe how bad the unfiltered data looks on the display.
@pwfarnell When you leave the VRM Device Instance menu, you get requested to reboot the GX device. This is necessary for the VRM device instance to change. Have you done that?
The instances were set several weeks ago with several reboots before V3.70~49 was installed. I have just incremented the USB GPS to 102 and rebooted, but will not be back on the boat for some time.
Back when I had issues with device instance numbers, I had to remove both the h/w gps as well as delete the Node-RED virtual GPS node (and I believe even the nodes input/output nodes), and do multiple reboots to clear out all (virtual) GPS devices from the (GX) devices menu before starting over adding them from scratch. For lack of better wording there was something inherently ‘sticky’ about VenusOS keeping traces of those GPSses even after removal and reboots, real and virtual. I’m suspecting this recent change around using VenusOS/system speed values instead of the GPS device speed values directly, was meant to address what was causing that. As a matter of fact that issue steered us towards writing our own NMEA parser in Node-RED, bypassing the VenusOS USB GPS detection and NMEA parser code al together. Making thankful use of the virtual GPS and more or less coincidentally stumbling upon the ability to use raw NMEA data to implement a very effective first stage ‘unreliable measurement’ pre filter.
I would also like to see my engine temps on the boatpage.
Is it possible to use node-red to show temps?
Hi Peter, welcome to the forum. You can’t display multiple engine temps, yet. See also: Engine integration - #17 by UpCycleElectric
Confirmed working OK now I have changed USB GPS instance again and rebooted.
Great, thanks for checking!
Hi
created 2 new treads regarding 2 findings in V3.70, possibly it was not the correct place, sorry .
Are there any ideas how to fix this?
Both findings are on CerboGX and BBB ?
update 20251031: just unpacked a new Cerbo GX MK2 with version V3.34 installed , updated to V 3.70~49 large and both bugs are here.
@mpvader : am I posting this in the correct thread? (I ask because it looks like nobody has observed this too, no answers are coming and I am an old retired freak 
)
groeten uit Oostenrijk, Leopold
I think I found a bug in DESS:
Changing tariff in dess results in 15 minute tarrifs while 60 minutes tarrif is selected.
Only changing the tariff to 15 minutes, submitting it and changing it back to 60 minutes and submitting it solves this problem after a while.
Maybe I should bring this ‘bug?’ to the attention this group…
Where did you pick up such silly an idea of DESS picking up on any physical realities or, in your case, set limits thereof. The DESS SoC scheduler takes the lesser of the DESS specific to and from grid and battery limit settings and assumes that’s the truth, the whole truth and nothing but the truth. You better make sure you buy enough equipment to deliver. (…put obligatory smileys here…)
Safiery have lodged a new Product “Range Master AI” that uses empirical date to calculate the Drag parameters then apply this in a similar comcept of Reactive Power and Real Power to predict Range to Go at different RPM. Its a DAME submission to Metstrade in 2025. Whilst we are not using Venus OS for this product with electric propulsion tenders, we interface to Victron and Venus OS on sailing boats with hybrid electric drives using this product.
Great plug, made me grin ánd look you up. I’ll come visit your booth at Metstrade to meet your acquaintance and collect my complementary 48V alternator. Will check that range master as well although skeptical about the AI part: https://youtu.be/MtHiWcbhg-Y