Ah, I responded above thinking you already had ntfy set up. Ntfy is so cool, I definitely recommend taking a look at it. I use it for notifications from Home Assistant, Uptime Kuma, Proxmox, etc. There are other similar things out there like Gotify, but I seem to prefer ntfy.
walden
joined 2 years ago
I think if you're nerdy enough to self host stuff, you can definitely figure out LubeLogger. You don't have to use all aspects of it... you can just use it for tracking gas mileage if you want.
If you want it to keep track of maintenance like oil changes and stuff, you have to add them manually and tell it how often you want them done.
For tracking gas mileage and maintenance reminders, all you need are 3 tabs - Service Records, Fuel, and Reminders. You can ignore everything else.
I responded to someone below. Hope it helps.
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:
- Schedule when you want notifications (I like being reminded on monday, wednesday, and friday at 8am)
- Have Node-RED pull the maintenance reminders, which are available in JSON format
- 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).
- Feed the filtered data into templates -- different templates for each level of urgency. This adds some complexity, but I like it.
- 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).
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.
They can be charged below 0*C, too. No need to redirect lots of current to heating the batteries during charging like with Lithium.
I love LubeLogger. I've totally switched both my and my wifes cars to it for tracking gas mileage and maintenance.
If anyone would like, I can share how I got ntfy notifications working with it for maintenance reminders.
Most countries require flight crews to clear customs if they're on the ground for more than a certain amount of time. The only one I know off the top of my head is Canada, which requires it over 1.5 hours.
In reality, the timeline was likely 1) pilot messaged the company about the problem shortly into the flight, 2) company said "ok, keep going while we look into options, and 3) 30 minutes or an hour later they told the crew to turn around. Flight crews don't make logistical decisions in cases like this.
Good news, they just released v1.130.1
Motorcycles... it's always motorcycles.
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!
I've had a contractor put their foot through the ceiling accidentally. They fixed it, of course. I'm just glad it wasn't me.
From the GUI go to Datacenter - Notifications. Add a Notification Target of the Webhook type. Mine looks like this:
See the ntfy documentation for different types of authorization, tags (emojis), etc.
Then edit the default Notification Matcher and enable your new target.
By default I get notifications of successful/failed backup jobs. I want to set something up for drive health using SMART, but I'm just sitting down to figure that out now.