Android Tasker routine to warn if home WiFi is not functioning correctly
Been experiencing a bit of an issue the last month with everything seemingly on and connected, but my Chromecast device would not connect across Wi-Fi today, and sometimes my wife says her phone is not connecting, and I’d have to reboot the home rou ...continues
I was getting frustrated with the multiple versions of #Tasker plugin documentation, so I started creating a wiki article with up-to-date information and examples.
While the examples provided showed me what to copy-and-paste, I didn't understand how it all fit together or how to build something from scratch. This is my attempt at reducing pain for future developers (and future me!). Examples, tutorials, gotchas, and more.
My current obsession is sticking little NFC stickers on anything and everything to automate stuff with #Tasker as the trigger.
🚰 Tag on the water bottle? Scan to log water consumption.
🐕 Tag next to the dog leash? Start the #Toggl time entry for walking my dog.
📺 Two on the back of the TV remote for watching YouTube or movies (the movie one dims the lights).
👕 One on the washing machine to start a timer to remind me to put the clothes in the dryer.
Well, after a bit of fumbling, I'm releasing the first version of my first #Android app, Timekeeper.
Timekeeper is a #Tasker plugin to automate interacting with #Toggl Track for time tracking. My main use case is things like scanning NFC tags around the house when I'm doing various things.
It only does some basic time entry starting and stopping now, but it's a good starting point. If that's something you might benefit from, consider checking it out.
I use the HTTP request actions in #Tasker to automate the creation of time entries in #Toggl, but that's been pretty darn flaky for me recently. Not sure if that's my internet, my phone, or Toggl's API blocking my requests.
Tasker provides a library and POC code for creating native plugins. So, let's try that! It's an excuse to get back into some #Flutter development, and it'll force me to get exposed to #Gradle and #Kotlin.
Well, one day was a bit ambitious. But this is doable.
Struggle #1 is the learning of #Kotlin. I see some design parallels to Java (makes sense) and TypeScript. I have to think about the language, which means I'm spending less time thinking about the implementation.
Struggle #2 is getting more familiar with the #Flutter ecosystem and interacting with it from native code. Should I have started this with just a base Android project? Perhaps. But I'm nothing if not stubborn!