As has been mentioned here before, Signal K versions are a long way behind actual Signal K releases. This is a real pain, as many apps that are developed for Signal K can not be implemented until the version of Signal K is finally reached in Venus.
I see this has been raised before, but conveniently closed by the silly 14 day no comment rule…
Node Red is consistently up-to-date, why not Signal K.
Your question was about getting an update.
Updates fit within the victron cycle and signalK has apparently been troublesome to update in venus, so updates for update sake doesn’t happen.
What are you missing out on by not having the update or is it just FOMO?
A good motivation helps.
Also, nodered is not exactly up to date either..
The point isn’t to be at the latest revision, the whole ecosystem functioning correctly is the first priority.
I get that system stability and functionality has to be priority. But 5 months between releases?
If a new app is developed, in most cases it cannot be installed until the signal k version is up-to-date in Venus with the app development release.
With the speed Venus updates move at and release of new features/integrations, new signal k apps move at a similar speed to keep up with these new features/integrations, but cannot be accessed if running on signal k on Venus.
Ok thanks.
I know there has been a concerted effort to reduce the lag. This is beyond the community teams control, but it has been raised before. And again now. There does seem to be a plan to move it forward again with newer versions. Often these can be bumped into the incremental production releases that appear along the way.
Fingers crossed.
Look in the beta category, venus os beta section. The direction is always in the pinned release topic.