Sunrise and Sunset times are way off for my location

[h0ckeysk8er (Bruce Pinsky)]

@chunk_split

This was perfect, thanks! Super awesome and instant feedback, I appreciate it. I think it’s up-to-date now, then. So will double check later today to see if the lights are on too early again or not (since I made the change yesterday) just to confirm. Looks like it’s showing the coords directly on top of my house.

FWIW, for me the JSON output -j flag isn’t necessary, it’s already nicely formatted (at least if you’re using the CLI directly and not piping it into something else for processing, like JavaScript). I like this better

patnelson@compy386 ~/smartthings
$ ./smartthings locations 1
─────────────────────────────────────────────────────────
 Name               My home
 Location Id        abc123ab-c123-abc1-23ab-000000000000
 Country Code       USA
 Time Zone Id       America/Los_Angeles
 Background Image
 Latitude           45.51498617
 Longitude          -122.67886289
 Region Radius      250
 Temperature Scale  F
 Locale             en-US
─────────────────────────────────────────────────────────

Ah, good point. You have to use the -j option with the devices command to get the detail of your hub. I was just thinking in that same line of thought and didn’t try it without the -j

[chunk_split]

@orangebucket

I don’t know a way of finding out what the hub’s current info on that is, but the sunrise/sunset times for your Location can be pulled from the API on the URL

http://api.smartthings.com/services/coordinate/locations/{{locationId}}/capabilities?name=weather

Subject to a suitable bearer authentication of course.

Nice! Thanks. This also works well. I didn’t actually read any documentation at all, but this was straight to the point so it “just worked” for me. Just documenting my journey… just a few minor notes to get it to work:

1. That redirects to https:// (super minor caveat) but once you use that, it works.
2. After installing the CLI, I easily found a token I could use under ~/.config/@smartthings/cli/credentials.json, so at that point it was a simple matter of including Authorization: Bearear {{TOKEN}} HTTP header (I assumed they used this scheme, typical REST)

The final/full curl request is essentially:

export ST_TOKEN="YOUR-TOKEN-UUID"
export ST_LOCATION="YOUR-LOCATION-UUID"
curl -v -H "Authorization: Bearer $ST_TOKEN" "https://api.smartthings.com/services/coordinate/locations/$ST_LOCATION/capabilities?name=weather"

Which emits sunsetTimeLocal which is the local time of sunset (naturally in Zulu, lol, no TZ offset… so it’s local, but it’s not) but it resolves to 8:40pm for me which is exactly right for today for Portland. Great success.

[jkp]

you may want to reconsider posting your Latitude and Longitude info online. just a thought if you are concerned about privacy.

[chunk_split]

@jkp

you may want to reconsider posting your Latitude and Longitude info online. just a thought if you are concerned about privacy.

It was very intentional I was very deliberate on the specific coordinates I swapped in, hoping someone would catch on and comment on it, lol. My computer isn’t named compy386 either (that was just a reference).