• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: June 10th, 2023

help-circle









  • Since there’s no native ntfy notification built in to LubeLogger I figured out a way to do it using Node-RED. If you don’t have Node-RED set up, It’s pretty great for automating things. I mostly use it for Home Assistant. There’s certainly a way to accomplish this without Node-RED, but I would have no clue where to start.

    The basic idea of the flow attached below is:

    1. Schedule when you want notifications (I like being reminded on monday, wednesday, and friday at 8am)
    2. Have Node-RED pull the maintenance reminders, which are available in JSON format
    3. Do some filtering and splitting of the data, narrowing the reminders down to Past Due, Very Urgent, and Urgent (ignoring everything that doesn’t need attention).
    4. Feed the filtered data into templates – different templates for each level of urgency. This adds some complexity, but I like it.
    5. Bring everything back together, format it into something that ntfy.sh likes, and then fire the notification.

    You’ll of course have to go through and change settings in each node to match your LubeLogger URL and vehicle ID’s, and preferred ntfy server and topic. You can also add your username/password for LubeLogger and ntfy (or a bearer token, if that’s what you have set up with ntfy).

    Node-RED flow

    If you’re not familiar with Node-RED, you’d import the above JSON and edit it from there. Stuff “flows” through nodes, stopping and doing what you tell it along the way.





  • I finally figured out how to get the terrain stuff going on my Wanderer. Super cool!

    Now I’m trying to figure out my future workflow… can you shed some light on it?

    Currently everything I upload is its own “Trail”. This goes for the Strava integration, as well as me just uploading a GPS track.

    Trails are nice because they all show up on the Map, making a cool overview of everything I’ve done. Obviously over time this might bog down the system when viewing the map.

    Trails aren’t included in the statistics, which is a bummer.

    So, I played around with moving each of my activities into broader “trails”, based on where the activity took place. I think that’s probably how Wanderer is supposed to be used, because when I move activities from being a “Trail” to being a “Summit”, they are counted in the statistics.

    The only downside to that is they don’t appear on the map, unless you click the specific Summit.

    So, basically, my question is – should I just accept the fact that I should move everything into being a Summit, so I can enjoy the statistics?

    Thanks!