question

Don't you find relevant content in sub-driectory "dunfell"?

Yeah I noticed this too.

Also it seems perhaps something in the VRM backend could also have been changed. My very functional jessie and buster setup are now only communicating once a day, and for the rest of the day show as off-line. Using the diagnostic URL within vrm it shows up and records the first attempt but none after that until a (scheduled, or manual) restart.

I've flagged the jessie/buster removal on the github a week and a bit ago also without any update or clarification. Hope this can be restored and the VRM functionality returned. Otherwise I'll have to install another ESXI based raspberry pi venusos image. But with the chip shortage impacting the availability of 8g rpi4s I'd rather keep using my rpi3b+ if I could.

I've found a workaround: Most of the packages (localsettings, vrmlogger, dbus-mqtt) are Python and will run anywhere. So I downloaded the latest Venus OS image and extracted those services from that image. I manually copied them onto my Raspian setup and it works! For dbus-mqtt I had to manually install mosquitto and configure persmissions.

The only package that required a bit of elbow grease was vedirect-interface. I had to manually install libevents and libevents_pthreads and add some symlinks to make version numbers match up.

I have it all working on Raspberry Pi Zero 2 W now, VRM portal and all. I'm not seeing the issue you are describing with the VRM portal - maybe it's because they changed something and I am running vmrlogger from the very latest Venus OS image.

Seems they are back - in the following form.....

https://updates.victronenergy.com/feeds/venus/candidate/packages/raspbian-buster

as well as

https://updates.victronenergy.com/feeds/venus/candidate/packages/debian-buster/

@mvader (Victron Energy) kindly updated https://github.com/victronenergy/venus/wiki/install-venus-packages-on-Debian 28 days ago. Made minor adjustments according to reflecting buster over jessie etc.

https://github.com/victronenergy/venus/wiki/install-venus-packages-on-Debian/_compare/341e7d000ccd04f603b272b0fb013fb6d203bf05...e6338bb31de62708f6eb39ae5b002751832e5cab

Also noting that release and candidate changes are clearly listed now. My setup was for some reason always candidate and its now bitten me.... hard!

I made the mistake of doing a full apt update and upgrade and well things went south.

VRM is no longer showing on the dashboard any status since the change. Thankfully the diagnostic page is reflecting the important data - so things are reaching the vrm platform. I notice that a few values are stale and have not received an update.

Was working on vrmlogger_2.205-r0 and prior - but not so happy with vrmlogger_2.255

/var/cache/apt/archives/vrmlogger_2.205-r0.0_armhf.deb

/var/cache/apt/archives/vrmlogger_2.255-r0.0_armhf.deb

/var/cache/apt/archives/vrmlogger_2.203-r0.0_armhf.deb

46192 Jun 16 21:10 can-bus-bms_0.38-r0.0_armhf.deb

43864 Jun 16 21:10 dbus-adc_1.37-r0.0_armhf.deb

42074 Jun 16 21:10 dbus-ble-sensors_0.10-r0.0_armhf.deb

40956 Jun 16 21:10 dbus-bornay-windplus_1.6.0-r0.0_armhf.deb

85370 Jun 16 21:10 dbus-digitalinputs_0.15-r0.0_armhf.deb

33240 Jun 16 21:10 dbus-imt-si-rs485tc_1.1.7-r0.0_armhf.deb

33764 Jun 16 21:10 dbus-modem_0.16-r0.0_armhf.deb

24212 Jun 16 21:10 dbus-motordrive_1.10-r0.0_armhf.deb

271734 Jun 16 21:10 dbus-systemcalc-py_2.102-r0.0_armhf.deb

27902 Jun 16 21:10 dbus-valence_1.14-r0.0_armhf.deb

28356 Jun 16 21:10 dbus-vebus-to-pvinverter_1.32-r0.0_armhf.deb

32118 Jun 16 21:10 gps-dbus_1.07-r0.0_armhf.deb

143508 Jun 16 21:10 mk2-dbus_3.39-r0.0_armhf.deb

51006 Jun 16 21:10 mk3selftest_1.04-r0.0_armhf.deb

780 Jun 16 21:10 packagegroup-ve-dbus-data-producers_1.0-r0.0_armhf.deb

118876 Jun 16 21:10 vecan-dbus_2.90-r0.0_armhf.deb

3616 Jun 16 21:10 velib-canhw-socketcan_1.02-r0.0_armhf.deb

132394 Jun 16 21:10 vrmlogger_2.255-r0.0_armhf.deb