grimmace92 wrote: 
> Here is what I'm doing in putty and what I see.  Something with my
> certificate is causing an issue.  I just have no idea what else to
> check.  Port 443 is forwarded to 8123.  For this line is it supposed to
> stay like this or is the whole thing supposed to be replaced with the
> token?  
> 
> For example this:
> 
> https://HA_Link.duckdns.org/api/states/sensor.art_ID? -H "Authorization:
> Bearer $HA_Token"
> 
> should become this?
> 
> https://*mynameused*.duckdns.org/api/states/sensor.art_ID? -H
> "Authorization: Bearer $HA_Token"
> 
> or this
> 
> https://mynameused.duckdns.org/api/states/sensor.art_ID? -H
> "Authorization: *the_token_generated_from_duckdns*"
> 
> 

The line is supposed to be this: 
https://mynameused.duckdns.org/api/states/sensor.art_ID? -H
"Authorization: Bearer $HA_Token"
The second line of the shell script files (ie: qry_alb.sh) should read
*HA_Token=Your_Long_Lived_Token_Here*.  Replace
"Your_Long_Lived_Token_Here" with the Home Assistant generated token
using the procedure I sent yesterday.  You should create a dedicated
long lived access token for the Dialogflow / shell scripts.

As for the output from the script, a few things:
    
- Looks like your system does not have the command "nc" installed. 
  You need this to make it work or you can use "socat" but that would
  require some minor changes in the query statements
- Also the results did not get posted because the curl statement got a
  certificate error which could be due to several different things. 
  Improper HA_Token which is likely if you used the duckdns certificate
  as your HA token.  Also make sure you can access HA GUI directly from
  the internet using https://yourdomain.duckdns.org.  The https: part is
  important and it won't work otherwise in dialogflow.
- 
  

Re-reading your previous posts I notice that you created certificates
and such for let's encrypt.  Generally if your just using the duckdns
addon, all that let's encrypt stuff should just happen automatically
provided you accepted the terms in the config file when setting up HA's
duckdns addon package.  Carefully check the duckdns setup part.

Ynot  

Ynot.



*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

Reply via email to