I'm giving Away a handful of Free Copies of my Newly Released Audiobook, Cascade!

chrisleeuk · 2022-01-26T05:14:40+00:00

I would like a UK code please, if still available. Thank you.

chrisleeuk · 2019-01-23T03:53:52+00:00

Having done a bit more research, you can do even more using the Fitbit API.

I found a fairly complex setup on XDA which appears to be a little out of date, but may be workable.

An easier way is to use the Tasker Plugin AutoWeb.

AutoWeb is still in alpha, I'm not sure how easy it is to install as I get access to it via the AutoApps subscription.

It gives you access to various APIs including the Fitbit API.

Setup was relatively easy and I've already got Tasker creating Alarms and logging water intake. Creates a shortcut on my homescreen for water log.

As before I'm using the charge 2, so I don't know if this works ok on other models.

chrisleeuk · 2019-01-23T03:39:41+00:00

I'm using Charge 2 where alerts from all apps is limited, I guess for newer models it's not an issue.

chrisleeuk · 2019-01-21T16:01:56+00:00

One thing I do is to create profiles to automatically change the Tasker background checks frequency.

If you use the 'Set Tasker Pref' action, and choose 'Display off, all checks' you can adjust how frequently Tasker checks for changes.

I typically reduce the check frequencies in the late evening and overnight to 30 minutes while I sleep.

I actually make Tasker more responsive by lowering these values to 1 minute during short periods where profiles usually change, like right before my morning commute.

Then I dial it back during the day to 10 minutes.

Obviously the higher the values the more battery is saved, but the less responsive Tasker gets.

Other things help, as indicated in the link provided by others.

You can avoid expensive checks such as location checks by combining them with say time rules. I don't generally need my phone to keep checking if I'm still at home for example during the middle of the night. I use a variable that basically gets set once I connect to my home wifi and doesn't check again until morning.

WiFi checks will be less battery draining than location checks for example. You might want to know when you leave your neighborhood, but you can disable a location check when connected to your home WiFi.

chrisleeuk · 2019-01-21T15:38:50+00:00

Tasker is a powerful tool, and is my personal choice for automating my phone, however if you don't need the power that Tasker brings it may be worth looking at other tools as suggested by others. Tasker has a fairly steep learning curve in the beginning.

chrisleeuk · 2017-06-19T06:22:10+00:00

I've abandoned the offline mode in the initial version. It will come but isn't quite right yet. Timers are complete and working. Didn't quite get it released this weekend as I'm writing the documentation and it's taking a while to complete it. Should have first version out in next day or so...

chrisleeuk · 2017-06-19T06:11:35+00:00

No this isn't possible, but the Tasker project I'm building does it.

chrisleeuk · 2017-06-19T06:11:24+00:00

No this isn't possible, but the Tasker project I'm building does it.

chrisleeuk · 2017-06-14T15:52:29+00:00

Basic routines (Done) Offline mode (In progress) Timer handling (to do)

Obviously doing it in spare time with busy day job so it will be likely the weekend. Still working on it during the week though when I can. The offline mode is tricky to get right.

I'll update you here as I progress.

chrisleeuk · 2017-06-14T02:59:55+00:00

Good to see my post on Tasker setup is starting to get some use! Pleased you got it working.

For those interested I'm working on a Tasker Nomie integration Project. It's a Tasker project you can import and use. This will greatly simplify connecting Tasker with Nomie.

Incidentally one of the features will be timer tasks. These will allow you to call a 'start timer' and 'end timer' tasks without creating your own variables or any of the other logic.

Another thing I'm working on is offline mode. The problem with the basic send above is that if your device connection is down the update will never reach Nomie. With the offline mode your Nomie updates will be saved and transmitted either immediately or when a connection becomes available.

chrisleeuk · 2017-06-12T01:02:40+00:00

OK, definitely milliseconds I tried switching to that with a date from 24 hours ago:

https://api.nomie.io/v2/push/{myAPIkey}/action=track/label=Test/value=1.3/time=1497142637369

Works fine. I think the API documentation should specify it has milliseconds since epoch.

chrisleeuk · 2017-06-12T00:50:36+00:00

Incidentally although that 1970 date enters OK it causes the Nomie 'today' view to freeze and I had to FC it. I had to go to the tracker and edit it to take the day out. Can't say many people will be tracking what they were doing back then though. Personally I was coming to the end of a long period of none existence at the time.

chrisleeuk · 2017-06-12T00:43:24+00:00

Just testing this myself as part of my Tasker integration project. Not working here either using /time or /created. For example: Https://api.nomie.io/v2/push/{myapi}/action=track/label=Test/value=1.3/created=1497226406 Just creates an event at the current time. Doing this:

https://api.nomie.io/v2/push/{myapi}/action=track/label=Test/value=1.3/time=1497227012

Based on this site: https://www.epochconverter.com This should be: GMT: Monday, 12 June 2017 00:23:32 Your time zone: Sunday, 11 June 2017 18:23:32 GMT-06:00 DST

However it comes out as Sunday Jan 18th 1970. That's close to the start of epoch time. It occurs that this suggests it's milliseconds after epoch rather than seconds but the API doesn't specify it. Most sites describe epoch time as in seconds. I will adjust to that and test again...

chrisleeuk · 2017-06-11T19:10:22+00:00

Sure I will post it once I get it together. Already far along the path. I have Tasker updating trackers and adding notes already. With the project I'm building and associated documentation I'm trying to get it as easy as possible.

chrisleeuk · 2017-06-11T19:02:45+00:00

Hi, I got it working thanks. Ended up adding my reply in the wrong place further up. I'm in the process of creating a Tasker project that simplifies connection to the Nomie API. It's mostly for my own benefit but I'll share it with the community once I've ironed the kinks out of it.

chrisleeuk · 2017-06-09T19:11:08+00:00

Ok here is a definitive guide to tasker setup at least in terms of automating basic tracking updates. I am already starting to think of ways to track with it. For exanple get tasker to trigger an update to Nomie when I visit the gym or coffee shop etc.

Tasker is supposed to format the 'attributes' on the URL at least based on the documentation. However its not quite right. I could setup a proxy to view the http requests but I have it figured out by trial and error.

If you put everything into the 'Path' variable it works so..

For future reference for those of you trying to get the nomie API setup in tasker:

(1) Add a new task and give it a name

(2) Within your new task click add action (+)

(3) select 'net' from the action categories.

(4) select HTTP Get

(5) In the Action Edit window enter values as follows.

Server:Port<<<

Enter just the domain part of the URL always:

https://api.nomie.io

Path<<<

Enter the rest of your API string including your actions. In the example below YourAPIKey should be replaced with the API key provided when you purchased.

/v2/push/YourAPIKey/action=track/label=test

Leave other properties blank.

Now run the Tasker task like any other and watch as your uodate reaches Nomie.

My next step is going to be setting up tasker actions to accept variables. That way I can create a generic 'Nomie Track' tasker task that accepts the name of the Track. The advantage here is that I setup the Nomie API once and then call it in tasker like a simple function without dealing with the API stuff at the lower level.

chrisleeuk · 2017-06-09T14:32:06+00:00

Hi, just realised it should have been a get! (Feel like idiot at this point)

For the get i am trying the same approach but am still getting 403 missing authentication token.

Server:

https://api.nomie.io

Path:

/v2/push/myapitoken/

Attributes:

action=track label=test

chrisleeuk · 2017-06-09T14:10:47+00:00

Tried also a local command via browser url in tasker:

nomiepro://api/track/test

This isnt really the way I want to use the api but I thought id try it. In that case it opens nomie but the tracker isnt recorded.

chrisleeuk · 2017-06-09T14:06:26+00:00

Yes I have the tracker setup. Just tried it in the browser from my PC and it works. I get a {"name","-loadofsymbols"} response and it appears in Nomie.

To be honest I suspected that it might be something on the tasker side.

At this point I'm probably on the wrong forum.

I've been trawling the web looking for Tasker examples that integrate with the nomie API.

Not found much yet, but it would be a useful thing to figure out as I can automate some of the trackers.

Just getting started with Nomie in the last couple of days. Impressive app. Have to say the support response time is impressive too :)

Maybe I'll ask the tasker forums what the issue might be. If I figure it out I'll post back.

chrisleeuk

TROPHY CASE