Go with emulated hue.
you give up on me? 
Yeah. If this is confusing you, then emulated hue is the way to go. If you wanna work on it some more, start by making your HASS reachable from outside your network.
I have this problem trying to
Failed authorization procedure. hass-xxx.duckdns.org (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: DNS problem: NXDOMAIN looking up A for hass-xxx.duckdns.org
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: hass-xxx.duckdns.org
Type: connection
Detail: DNS problem: NXDOMAIN looking up A for
hass-xxx.duckdns.org
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
pi@raspberrypi:~/certbot $
I donāt use DuckDNS, but that looks like you did something wrong in setting up your DuckDNS account.
yes, that is only settings that is not working. Tried TOR was too hard for me, tried AWS lamba even worse. Hope to get this letsencrypt and duckdns fixed soon
Oh, wait - is that an error log from running the LetsEncrypt program? If so, you either:
- didnāt set up your domain correctly on the DuckDNS site. You can test this with an nslookup.
- didnāt set up port forwarding on your router. You need to forward 80 and 443 (and have HASS turned off when you run the script) to your HASS install
ahh, I forwarded 80, not 443 (443, not 433 right?).
HASS turned off? You mean switching off the raspberry pi, or?
I think thats ok. I do you use nslookup?
443 Correct. How would you run the command on the pi if you had it turned off? You need to stop HASS. Use the services tab - thatās the easiest way.
Google nslookup. You can do it!
Based on your questions in the media_player thread, Iād recommend holding off on this. Looks like you need to understand automations before itād be helpful to have Alexa skills integration.
you over estimate me ahah
Yeah - you donāt want to be messing around with Flash Briefings. You want an Alexa Skill.
Also, Iāve heard there are still-unresolved issues with using the Flash Briefing with SSL.
whatever I say after āAlexa, ask deedee to ā¦ā
I get the answer
āthe requested skill took too long to respondā
Did you complete everything at the URL in my previous post?
Inside of the Alexa Skills interface, thereās a way to test from there. Itāll show the response it receives from your Home Assistant interface.
Make sure you set up your intents in your YAML, too.
it gives this
{
"session": {
"sessionId": "SessionId.11f5ef3f-5eba-4c2f-b131-4a4f6f68958f",
"application": {
"applicationId": "amzn1.ask.skill.4f934f14-5033-4939-9020-985e9a86038f"
},
"attributes": {},
"user": {
"userId": "amzn1.ask.account.Axxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
},
"new": true
},
"request": {
"type": "IntentRequest",
"requestId": "EdwRequestId.39908e1a-837e-4a1c-9f5c-e4ed47ecf143",
"locale": "en-US",
"timestamp": "2016-12-21T20:31:37Z",
"intent": {
"name": "LocateIntent",
"slots": {
"User": {
"name": "User",
"value": "where {User}"
}
}
}
},
"version": "1.0"
}
and on the right
There was an error calling the remote endpoint, which returned HTTP 405 : Method Not Allowed
That means itās having trouble talking to HASS.
Did you configure an intent called āLocateIntentā?
That appears to be what youāre trying to trigger. You need YAML for each intent that you set up.
Intents work a lot like scripts. Start easy with an intent that turns a light on and replies with some spoken text.
did copy paste from your link)
alexa:
intents:
WhereAreWeIntent:
speech:
type: plaintext
text: >
{%- if is_state('device_tracker.3966da76', 'home') and
is_state('device_tracker.lillian_iphone5', 'home') -%}
You are both home, you silly
{%- else -%}
Lillian is at {{ states("device_tracker.lillian_iphone5") }}
and Claudio is at {{ states("device_tracker.3966da76") }}
{% endif %}
LocateIntent:
action:
service: notify.notify
data_template:
message: The location of {{ User }} has been queried via Alexa.
speech:
type: plaintext
text: >
{%- for state in states.device_tracker -%}
{%- if state.name.lower() == User.lower() -%}
{{ state.name }} is at {{ state.state }}
{%- endif -%}
{%- else -%}
I am sorry, I do not know where {{ User }} is.
{%- endfor -%}
card:
type: simple
title: Sample title
content: Some more content
ActivateSceneIntent:
action:
service: scene.turn_on
data_template:
entity_id: scene.{{ Scene | replace(" ", "_") }}
speech:
type: plaintext
text: OK
flash_briefings:
whoishome:
- title: Who's at home?
text: >
{%- if is_state('device_tracker.3966da76', 'home') and
is_state('device_tracker.lillian_iphone5', 'home') -%}
You are both home, you silly
{%- else -%}
Lillian is at {{ states("device_tracker.lillian_iphone5") }}
and Claudio is at {{ states("device_tracker.3966da76") }}
{% endif %}
Are you using device_trackerās in your configuration? If not, Iām not sure what that code will do.
Like I said, start with something simple.
Could also be that your HASS isnāt reachable from outside the network, though I seem to recall that checking this is a step to getting an Alexa skill set up in the first place.
yes
the two device_tracker in the code itās me and my wifeās phone.
The HASS is reachable, I just checked it