grimmace92 wrote:
> I'm pretty close to getting this working.
> Update https://HA_Link.duckdns.org/api/states/sensor.art_ID? -H
> "Authorization Bearer $HA_Token" with you're HA_Link (must be accessible
> from the internet)
>
> I assumed this meant to change "HA_Link" to what you created in duck dns
> and also to replace "Authorization Bearer $HA_Token" with the duck dns
> token leavin the quotes. Is that correct?
Hi,
- The HA_Link is to be replaced with your domain line name. So mine
might be (but isn't) ynotmylink.duckdns.org
- The HA Token needs to be generated for your application. It is a
long lived access token and allows other applications (shell scripts
and DialogFlow app) to access the HA instance. It's the new security
model implemented as of version 0.80. You can create it from your
profile page (click on your initials) in HA. When you create it you
will be given the HA token code, copy it and keep it secure it's the
only time you get to see it. Then for each shell script, it needs to
be copied into the line *HA_Token=Your_Long_Lived_Token_Here*
- Also note that some systems require a : between "Authorization*:*
Bearer $HA_Token"
*software* - logitech media server version: 7.9.1, home assistant
0.75.3, dialogflow - v.2 api, lms controls app - voice control of lms,
openmediavault 4.1.9 - storage
*add-ons* - spotty, upnp / dlna bridge, chromecast bridge,
*players* - sonos, upnp, pi3 - pi core player 3.5.0, android- sb player
v1.4.0, airplay to googlehome and minis
*hardware* - server - i7-3.4ghz, 4gb ram, 6tb storage, debian - 4.16.5
------------------------------------------------------------------------
ynot1234567890's Profile: http://forums.slimdevices.com/member.php?userid=66569
View this thread: http://forums.slimdevices.com/showthread.php?t=109273
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins
