Core: Nabu Casa not sending devices to alexa. Alexa Discover devices gives "No new devices found."
Home Assistant release with the issue:
0.98.4 (also tried against 0.96.3)
Last working Home Assistant release (if known):
Hasn't worked for me yet.
Operating environment (Hass.io/Docker/Windows/etc.):
hass.io on Ubuntu
Component/platform:
Nabu Casa Alexa integration
Description of problem:
New setup of alexa via Nabu Casa, but can't get it to recognize any devices. I suspect regional issues as my first alexa device was purchased in US, but I live in europe and have accounts in Amazon US, DE, and UK. Unsure what to do about it though.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
cloud:
And followed all the instructions here and ensure all entities were set to publish to alexa.
Also tried being more explicit in configuration.yaml like:
alexa:
filter:
include_domains:
- alert
- automation
- cover
- fan
- group
- input_boolean
- light
- lock
- media_player
- scene
- script
- sensor
- switch
But didn't change much except I had fewer entities set to publish.
Traceback (if applicable):
This is the only thing I've found in the logs that really talks about alexa
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/alexa/state_report.py", line 125, in async_send_add_or_update_message
alexa_entity = ENTITY_ADAPTERS[domain](
KeyError: 'zwave'
Here's what I get after I tell it to sync devices to amazon.
2019-09-04 23:17:39 DEBUG (SyncWorker_1) [homeassistant.components.evohome] Status = {'systemId': '4187037', 'zones': [{'zoneId': '4187036', 'temperatureStatus': {'temperature': 25.5, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 18.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Living Room'}, {'zoneId': '4217766', 'temperatureStatus': {'temperature': 22.0, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 20.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Dining Room'}, {'zoneId': '4217767', 'temperatureStatus': {'temperature': 21.5, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 18.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Entrance'}, {'zoneId': '4217768', 'temperatureStatus': {'temperature': 22.0, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 22.0, 'setpointMode': 'FollowSchedule'}, 'name': 'Laundry room'}, {'zoneId': '4217769', 'temperatureStatus': {'temperature': 23.5, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 22.0, 'setpointMode': 'PermanentOverride'}, 'name': "Sebastian's Room"}, {'zoneId': '4217770', 'temperatureStatus': {'temperature': 22.5, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 21.0, 'setpointMode': 'PermanentOverride'}, 'name': "Sophie's Room"}, {'zoneId': '4217771', 'temperatureStatus': {'temperature': 23.0, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 21.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Guest Bedroom'}, {'zoneId': '4217772', 'temperatureStatus': {'temperature': 24.0, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 22.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Master Closet'}, {'zoneId': '4217773', 'temperatureStatus': {'temperature': 23.0, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 21.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Master Bedroom'}, {'zoneId': '4217774', 'temperatureStatus': {'temperature': 21.5, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 18.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Garage'}, {'zoneId': '4217775', 'temperatureStatus': {'temperature': 22.5, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 21.5, 'setpointMode': 'PermanentOverride'}, 'name': 'Office & Library'}, {'zoneId': '4217776', 'temperatureStatus': {'temperature': 24.5, 'isAvailable': True}, 'activeFaults': [], 'setpointStatus': {'targetHeatTemperature': 22.0, 'setpointMode': 'PermanentOverride'}, 'name': 'Master Bath'}], 'activeFaults': [], 'systemModeStatus': {'mode': 'Auto', 'isPermanent': True}}
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=climate.living_room, old_state=<state climate.living_room=heat; hvac_modes=['off', 'heat'], current_temperature=26.0, min_temp=5.0, max_temp=25.0, temperature=18.0, hvac_action=heating, preset_mode=permanent, preset_modes=['none', 'temporary', 'permanent'], status=zoneId=4187036, activeFaults=[], setpointStatus=targetHeatTemperature=18.0, setpointMode=PermanentOverride, temperatureStatus=temperature=26.0, isAvailable=True, setpoints=current=from=2019-09-04T18:00:00+00:00, temperature=18.0, next=from=2019-09-05T00:00:00+00:00, temperature=18.0, friendly_name=Living Room Temperature, icon=mdi:radiator, supported_features=17 @ 2019-09-04T22:00:02.296506+02:00>, new_state=<state climate.living_room=heat; hvac_modes=['off', 'heat'], current_temperature=25.5, min_temp=5.0, max_temp=25.0, temperature=18.0, hvac_action=heating, preset_mode=permanent, preset_modes=['none', 'temporary', 'permanent'], status=zoneId=4187036, activeFaults=[], setpointStatus=targetHeatTemperature=18.0, setpointMode=PermanentOverride, temperatureStatus=temperature=25.5, isAvailable=True, setpoints=current=from=2019-09-04T18:00:00+00:00, temperature=18.0, next=from=2019-09-05T00:00:00+00:00, temperature=18.0, friendly_name=Living Room Temperature, icon=mdi:radiator, supported_features=17 @ 2019-09-04T22:00:02.296506+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.living_room_temperature, old_state=<state sensor.living_room_temperature=26; unit_of_measurement=C, friendly_name=Temperature-Living Room, device_class=temperature @ 2019-09-04T23:11:39.264067+02:00>, new_state=<state sensor.living_room_temperature=25; unit_of_measurement=C, friendly_name=Temperature-Living Room, device_class=temperature @ 2019-09-04T23:17:40.338285+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event automation_triggered[L]: name=Living Room Last Temp, entity_id=automation.living_room_last_temp>
2019-09-04 23:17:40 INFO (MainThread) [homeassistant.components.automation] Executing Living Room Last Temp
2019-09-04 23:17:40 INFO (MainThread) [homeassistant.helpers.script] Script Living Room Last Temp: Running script
2019-09-04 23:17:40 INFO (MainThread) [homeassistant.helpers.script] Script Living Room Last Temp: Executing step call service
2019-09-04 23:17:40 ERROR (MainThread) [homeassistant.helpers.service] Error rendering data template: UndefinedError: homeassistant.helpers.template.AllStates object has no element 18.0
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=automation.living_room_last_temp, old_state=<state automation.living_room_last_temp=on; last_triggered=2019-09-04T23:11:39.278533+02:00, id=living_room_last_temp, friendly_name=Living Room Last Temp @ 2019-09-04T22:13:38.240456+02:00>, new_state=<state automation.living_room_last_temp=on; last_triggered=2019-09-04T23:17:40.356007+02:00, id=living_room_last_temp, friendly_name=Living Room Last Temp @ 2019-09-04T22:13:38.240456+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event automation_triggered[L]: name=Living Room Last Mode, entity_id=automation.living_room_last_mode>
2019-09-04 23:17:40 INFO (MainThread) [homeassistant.components.automation] Executing Living Room Last Mode
2019-09-04 23:17:40 INFO (MainThread) [homeassistant.helpers.script] Script Living Room Last Mode: Running script
2019-09-04 23:17:40 INFO (MainThread) [homeassistant.helpers.script] Script Living Room Last Mode: Executing step call service
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=input_select, service=select_option, service_data=entity_id=input_select.living_room_last_preset_mode, option=<template DomainStates('permanent')>>
2019-09-04 23:17:40 WARNING (MainThread) [homeassistant.components.input_select] Invalid option: <template DomainStates('permanent')> (possible options: none, permanent, temporary)
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=automation.living_room_last_mode, old_state=<state automation.living_room_last_mode=on; last_triggered=2019-09-04T23:11:39.286686+02:00, id=living_room_last_preset_mode, friendly_name=Living Room Last Mode @ 2019-09-04T22:13:38.246136+02:00>, new_state=<state automation.living_room_last_mode=on; last_triggered=2019-09-04T23:17:40.368819+02:00, id=living_room_last_preset_mode, friendly_name=Living Room Last Mode @ 2019-09-04T22:13:38.246136+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.discworld_cpu_load_total, old_state=<state sensor.discworld_cpu_load_total=61; attribution=Data provided by Synology, unit_of_measurement=%, friendly_name=discworld CPU Load (Total), icon=mdi:chip @ 2019-09-04T23:02:12.162730+02:00>, new_state=<state sensor.discworld_cpu_load_total=62; attribution=Data provided by Synology, unit_of_measurement=%, friendly_name=discworld CPU Load (Total), icon=mdi:chip @ 2019-09-04T23:17:40.959387+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.discworld_network_down, old_state=<state sensor.discworld_network_down=1492.7; attribution=Data provided by Synology, unit_of_measurement=Kbps, friendly_name=discworld Network Down, icon=mdi:download @ 2019-09-04T23:02:12.171565+02:00>, new_state=<state sensor.discworld_network_down=1369.5; attribution=Data provided by Synology, unit_of_measurement=Kbps, friendly_name=discworld Network Down, icon=mdi:download @ 2019-09-04T23:17:40.970879+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.discworld_network_down_mbit, old_state=<state sensor.discworld_network_down_mbit=1.45771484375; unit_of_measurement=Mbit/s, friendly_name=Discworld Network Down Mbit @ 2019-09-04T23:02:12.174564+02:00>, new_state=<state sensor.discworld_network_down_mbit=1.33740234375; unit_of_measurement=Mbit/s, friendly_name=Discworld Network Down Mbit @ 2019-09-04T23:17:40.975055+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.discworld_network_up, old_state=<state sensor.discworld_network_up=46.4; attribution=Data provided by Synology, unit_of_measurement=Kbps, friendly_name=discworld Network Up, icon=mdi:upload @ 2019-09-04T23:02:12.178059+02:00>, new_state=<state sensor.discworld_network_up=313.4; attribution=Data provided by Synology, unit_of_measurement=Kbps, friendly_name=discworld Network Up, icon=mdi:upload @ 2019-09-04T23:17:40.978779+02:00>>
2019-09-04 23:17:40 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.discworld_network_up_mbit, old_state=<state sensor.discworld_network_up_mbit=0.0453125; unit_of_measurement=Mbit/s, friendly_name=Discworld Network Up Mbit @ 2019-09-04T23:02:12.180747+02:00>, new_state=<state sensor.discworld_network_up_mbit=0.3060546875; unit_of_measurement=Mbit/s, friendly_name=Discworld Network Up Mbit @ 2019-09-04T23:17:40.984086+02:00>>
2019-09-04 23:17:44 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.right to 10.10.10.4 (auth: True)
2019-09-04 23:17:44 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.front to 10.10.10.4 (auth: True)
2019-09-04 23:17:44 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.left to 10.10.10.4 (auth: True)
2019-09-04 23:17:44 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.back to 10.10.10.4 (auth: True)
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: env
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: assume-role
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: shared-credentials-file
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: custom-process
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: config-file
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: ec2-credentials-file
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: boto-config
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: container-role
2019-09-04 23:17:47 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: iam-role
2019-09-04 23:17:48 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.memory_use_percent, old_state=<state sensor.memory_use_percent=49.2; unit_of_measurement=%, friendly_name=Memory use (percent), icon=mdi:memory @ 2019-09-04T23:17:17.020807+02:00>, new_state=<state sensor.memory_use_percent=48.1; unit_of_measurement=%, friendly_name=Memory use (percent), icon=mdi:memory @ 2019-09-04T23:17:48.011796+02:00>>
2019-09-04 23:17:48 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.processor_use, old_state=<state sensor.processor_use=6; unit_of_measurement=%, friendly_name=Processor use, icon=mdi:memory @ 2019-09-04T23:15:44.036335+02:00>, new_state=<state sensor.processor_use=8; unit_of_measurement=%, friendly_name=Processor use, icon=mdi:memory @ 2019-09-04T23:17:48.025726+02:00>>
2019-09-04 23:17:48 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=sensor.load_15m, old_state=<state sensor.load_15m=0.24072265625; unit_of_measurement= , friendly_name=Load (15m), icon=mdi:memory @ 2019-09-04T23:17:17.012976+02:00>, new_state=<state sensor.load_15m=0.23193359375; unit_of_measurement= , friendly_name=Load (15m), icon=mdi:memory @ 2019-09-04T23:17:48.030525+02:00>>
2019-09-04 23:17:48 DEBUG (SyncWorker_1) [homeassistant.components.gtfs.sensor] Timetable: []
2019-09-04 23:17:48 DEBUG (Thread-2) [sseclient] Dispatching keep-alive event, 4 bytes...
2019-09-04 23:17:48 DEBUG (Thread-2) [nest.nest] <<< keep-alive event
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.utils] Caught retryable HTTP exception while making metadata service request to http://169.254.169.254/latest/meta-data/iam/security-credentials/: Connect timeout on endpoint URL: "http://169.254.169.254/latest/meta-data/iam/security-credentials/"
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 160, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 80, in create_connection
raise err
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 70, in create_connection
sock.connect(sa)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botocore/httpsession.py", line 258, in send
decode_content=False,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 641, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 344, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 686, in reraise
raise value
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 603, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 355, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.7/http/client.py", line 1244, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 125, in _send_request
method, url, body, headers, *args, **kwargs)
File "/usr/local/lib/python3.7/http/client.py", line 1290, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1239, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 152, in _send_output
self.send(msg)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 236, in send
return super(AWSConnection, self).send(str)
File "/usr/local/lib/python3.7/http/client.py", line 966, in send
self.connect()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 183, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 165, in _new_conn
(self.host, self.timeout))
urllib3.exceptions.ConnectTimeoutError: (<botocore.awsrequest.AWSHTTPConnection object at 0x7f53e8f35c10>, 'Connection to 169.254.169.254 timed out. (connect timeout=1)')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botocore/utils.py", line 303, in _get_request
response = self._session.send(request.prepare())
File "/usr/local/lib/python3.7/site-packages/botocore/httpsession.py", line 282, in send
raise ConnectTimeoutError(endpoint_url=request.url, error=e)
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://169.254.169.254/latest/meta-data/iam/security-credentials/"
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.utils] Max number of attempts exceeded (1) when attempting to retrieve data from metadata service.
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.hooks] Event choose-service-name: calling handler <function handle_service_name_alias at 0x7f53ed0ab320>
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.hooks] Event creating-client-class.cognito-identity-provider: calling handler <function add_generate_presigned_url at 0x7f53ed0e7dd0>
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.args] The s3 config key is not a dictionary type, ignoring its value of: None
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.endpoint] Setting cognito-idp timeout as (60, 60)
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.client] Registering retry handlers for service: cognito-idp
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.hooks] Event choose-service-name: calling handler <function handle_service_name_alias at 0x7f53ed0ab320>
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.hooks] Event creating-client-class.cognito-identity-provider: calling handler <function add_generate_presigned_url at 0x7f53ed0e7dd0>
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.args] The s3 config key is not a dictionary type, ignoring its value of: None
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.endpoint] Setting cognito-idp timeout as (60, 60)
2019-09-04 23:17:48 DEBUG (SyncWorker_4) [botocore.client] Registering retry handlers for service: cognito-idp
2019-09-04 23:17:49 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.front to 10.10.10.168 (auth: True)
2019-09-04 23:17:49 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.left to 10.10.10.168 (auth: True)
2019-09-04 23:17:49 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.right to 10.10.10.168 (auth: True)
2019-09-04 23:17:49 DEBUG (MainThread) [homeassistant.components.http.view] Serving /api/camera_proxy/camera.back to 10.10.10.168 (auth: True)
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: env
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: assume-role
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: shared-credentials-file
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: custom-process
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: config-file
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: ec2-credentials-file
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: boto-config
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: container-role
2019-09-04 23:17:52 DEBUG (SyncWorker_4) [botocore.credentials] Looking for credentials via: iam-role
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.utils] Caught retryable HTTP exception while making metadata service request to http://169.254.169.254/latest/meta-data/iam/security-credentials/: Connect timeout on endpoint URL: "http://169.254.169.254/latest/meta-data/iam/security-credentials/"
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 160, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 80, in create_connection
raise err
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 70, in create_connection
sock.connect(sa)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botocore/httpsession.py", line 258, in send
decode_content=False,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 641, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 344, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 686, in reraise
raise value
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 603, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 355, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.7/http/client.py", line 1244, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 125, in _send_request
method, url, body, headers, *args, **kwargs)
File "/usr/local/lib/python3.7/http/client.py", line 1290, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1239, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 152, in _send_output
self.send(msg)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 236, in send
return super(AWSConnection, self).send(str)
File "/usr/local/lib/python3.7/http/client.py", line 966, in send
self.connect()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 183, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 165, in _new_conn
(self.host, self.timeout))
urllib3.exceptions.ConnectTimeoutError: (<botocore.awsrequest.AWSHTTPConnection object at 0x7f53e833d0d0>, 'Connection to 169.254.169.254 timed out. (connect timeout=1)')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botocore/utils.py", line 303, in _get_request
response = self._session.send(request.prepare())
File "/usr/local/lib/python3.7/site-packages/botocore/httpsession.py", line 282, in send
raise ConnectTimeoutError(endpoint_url=request.url, error=e)
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://169.254.169.254/latest/meta-data/iam/security-credentials/"
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.utils] Max number of attempts exceeded (1) when attempting to retrieve data from metadata service.
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.hooks] Event choose-service-name: calling handler <function handle_service_name_alias at 0x7f53ed0ab320>
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.hooks] Event creating-client-class.cognito-identity-provider: calling handler <function add_generate_presigned_url at 0x7f53ed0e7dd0>
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.args] The s3 config key is not a dictionary type, ignoring its value of: None
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.endpoint] Setting cognito-idp timeout as (60, 60)
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.client] Registering retry handlers for service: cognito-idp
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.hooks] Event choose-service-name: calling handler <function handle_service_name_alias at 0x7f53ed0ab320>
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.hooks] Event creating-client-class.cognito-identity-provider: calling handler <function add_generate_presigned_url at 0x7f53ed0e7dd0>
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.args] The s3 config key is not a dictionary type, ignoring its value of: None
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.endpoint] Setting cognito-idp timeout as (60, 60)
2019-09-04 23:17:53 DEBUG (SyncWorker_4) [botocore.client] Registering retry handlers for service: cognito-idp
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: env
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: assume-role
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: shared-credentials-file
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: custom-process
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: config-file
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: ec2-credentials-file
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: boto-config
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: container-role
2019-09-04 23:17:54 DEBUG (SyncWorker_7) [botocore.credentials] Looking for credentials via: iam-role
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.utils] Caught retryable HTTP exception while making metadata service request to http://169.254.169.254/latest/meta-data/iam/security-credentials/: Connect timeout on endpoint URL: "http://169.254.169.254/latest/meta-data/iam/security-credentials/"
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 160, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw)
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 80, in create_connection
raise err
File "/usr/local/lib/python3.7/site-packages/urllib3/util/connection.py", line 70, in create_connection
sock.connect(sa)
socket.timeout: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botocore/httpsession.py", line 258, in send
decode_content=False,
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 641, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/local/lib/python3.7/site-packages/urllib3/util/retry.py", line 344, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/local/lib/python3.7/site-packages/urllib3/packages/six.py", line 686, in reraise
raise value
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 603, in urlopen
chunked=chunked)
File "/usr/local/lib/python3.7/site-packages/urllib3/connectionpool.py", line 355, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/local/lib/python3.7/http/client.py", line 1244, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 125, in _send_request
method, url, body, headers, *args, **kwargs)
File "/usr/local/lib/python3.7/http/client.py", line 1290, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/http/client.py", line 1239, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 152, in _send_output
self.send(msg)
File "/usr/local/lib/python3.7/site-packages/botocore/awsrequest.py", line 236, in send
return super(AWSConnection, self).send(str)
File "/usr/local/lib/python3.7/http/client.py", line 966, in send
self.connect()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 183, in connect
conn = self._new_conn()
File "/usr/local/lib/python3.7/site-packages/urllib3/connection.py", line 165, in _new_conn
(self.host, self.timeout))
urllib3.exceptions.ConnectTimeoutError: (<botocore.awsrequest.AWSHTTPConnection object at 0x7f53ebd716d0>, 'Connection to 169.254.169.254 timed out. (connect timeout=1)')
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/botocore/utils.py", line 303, in _get_request
response = self._session.send(request.prepare())
File "/usr/local/lib/python3.7/site-packages/botocore/httpsession.py", line 282, in send
raise ConnectTimeoutError(endpoint_url=request.url, error=e)
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://169.254.169.254/latest/meta-data/iam/security-credentials/"
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.utils] Max number of attempts exceeded (1) when attempting to retrieve data from metadata service.
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.hooks] Event choose-service-name: calling handler <function handle_service_name_alias at 0x7f53ed0ab320>
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.hooks] Event creating-client-class.cognito-identity-provider: calling handler <function add_generate_presigned_url at 0x7f53ed0e7dd0>
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.args] The s3 config key is not a dictionary type, ignoring its value of: None
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.endpoint] Setting cognito-idp timeout as (60, 60)
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.client] Registering retry handlers for service: cognito-idp
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.hooks] Event choose-service-name: calling handler <function handle_service_name_alias at 0x7f53ed0ab320>
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.hooks] Event creating-client-class.cognito-identity-provider: calling handler <function add_generate_presigned_url at 0x7f53ed0e7dd0>
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.args] The s3 config key is not a dictionary type, ignoring its value of: None
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.endpoint] Setting cognito-idp timeout as (60, 60)
2019-09-04 23:17:55 DEBUG (SyncWorker_7) [botocore.client] Registering retry handlers for service: cognito-idp
Additional information:
cloud
scstraus
All 17 comments
Hey there @home-assistant/cloud, mind taking a look at this issue as its been labeled with a integration (cloud) you are listed as a codeowner for? Thanks!
![probot-home-assistant[bot] picture](https://avatars2.githubusercontent.com/in/36093?v=4&s=40)
probot-home-assistant[bot]
on 5 Sep 2019
I have also tried removing the homeassistant skill, de registering all Alexa devices and turning the integration off, restarting HA, and turning it on again and adding the device and skill again but no luck.
scstraus
on 11 Sep 2019
Also it looks like the one Alexa message I got in the log was due to a new zwave switch I was setting up. This one actually did finally make its way to Alexa. So I have one switch set up out of about 250 entities I told it to sync in the UI. The integration works, but it seems that HA just doesn鈥檛 want to send my devices there.
scstraus
on 11 Sep 2019
So I've tried deleting my nabu casa account and creating a new one and factory resetting my kindle and deregistering all devices but none of that helped.
Will no one help me? Am I doomed to forever have only 1 out of 216 devices enabled?
scstraus
on 27 Sep 2019
So I have put up a fix for the exception that you posted about ENTITY_HANDLERS. Once that is merged and released (0.100), please try again. For now, you can work around it by going to cloud -> alexa and making sure you don't enable any of the zwave.* entities.
balloob
on 27 Sep 2019
🎉1
I tried to remove all zwave devices but so far no luck.
Looking back, I think the entity exception was the one time it actually worked properly. I was adding a new zwave device and it wasn鈥檛 done adding to homeassistant yet (all its entities hadn鈥檛 shown up). Finally after a restart the entities were there and this ended up being the only device that made it over to Alexa.
The problem is, there鈥檚 simply no attempt at all to send the other 200 devices so they generate no log messages. I need to trigger something which forces it to resend all devices. The sync button does nothing from what I can tell.
I will try with 0.100 but I think you will probably see a new ticket on this.
scstraus
on 27 Sep 2019
Can you try saying "Alexa, discover devices" ?
balloob
on 27 Sep 2019
I've done it at least 50 times both verbally and through the UI on both my phone and my kindle fire. I've also clicked the "sync entities" button at least 80 times. They are simply not getting sent by homeassistant to Alexa. No log activity whatsoever.
I need some low level way to prod homeassistant to send these devices over. I'm happy to run a forked version or something which gives more debug information to figure out what the problem is..
I've tried every possible solution that seems open to me at this point.. It's just not sending the devices I had before trying to enable it. Only new devices like that Zwave one get sent.
scstraus
on 27 Sep 2019
Try adding this to your config so you can see the published messages:
logger:
default: info
logs:
hass_nabucasa: debug
homeassistant.components.cloud: debug
Also try removing the alexa: part under cloud: and use the UI to configure it.
balloob
on 1 Oct 2019
I didn't have the alexa: part under cloud:, I only tried it once to see if it would change anything..
my logger section looked like this:
logger:
default: debug
logs:
homeassistant.components.mqtt: warn
homeassistant.components.websocket_api: warn
homeassistant.components.deluge_client: warn
homeassistant.components.zwave: warn
homeassistant.components.openzwave: warn
homeassistant.components.libopenzwave: warn
So, it should have already had hass_nabucasa and homeassistant.components.cloud as debug, no? Anyhow, I am updating to:
logger:
default: debug
logs:
homeassistant.components.mqtt: warn
homeassistant.components.websocket_api: warn
homeassistant.components.deluge_client: warn
homeassistant.components.zwave: warn
homeassistant.components.openzwave: warn
homeassistant.components.libopenzwave: warn
hass_nabucasa: debug
homeassistant.components.cloud: debug
So I left it running and clicked on the sync entities button for the 80th time and here's what I can get from grepping the log for those items. There were some alexa messages this time (see pastebin link). Let me know if you want any more context on any of the below. Also, my config is available at https://github.com/scstraus/home-assistant-config
Here's the interesting looking log bit:
https://pastebin.com/B7gUFpad
scstraus@narnia:~/hassio/homeassistant$ grep components.cloud home-assistant.log
2019-10-06 01:16:17 DEBUG (SyncWorker_0) [homeassistant.util.json] JSON file not found: /usr/src/homeassistant/homeassistant/components/cloud/.translations/binary_sensor.en.json
2019-10-06 01:16:18 DEBUG (SyncWorker_0) [homeassistant.util.json] JSON file not found: /usr/src/homeassistant/homeassistant/components/cloud/.translations/en.json
scstraus@narnia:~/hassio/homeassistant$ grep nabucasa home-assistant.log
2019-10-06 01:16:10 INFO (MainThread) [hass_nabucasa.iot] Connected
2019-10-06 01:16:10 DEBUG (MainThread) [hass_nabucasa.iot] Publishing message:
2019-10-06 01:16:12 DEBUG (MainThread) [hass_nabucasa.cloud_api] Fetched https://remote-sni-api.nabucasa.com/register_instance (200)
2019-10-06 01:16:12 DEBUG (MainThread) [hass_nabucasa.remote] Retrieve instance data: {'status': 200, 'domain': '[REDACTED]', 'email': '[email protected]', 'server': 'eu-central-1.ui.nabu.casa'}
2019-10-06 01:16:14 DEBUG (MainThread) [hass_nabucasa.cloud_api] Fetched https://remote-sni-api.nabucasa.com/snitun_token (200)
2019-10-06 03:19:24 DEBUG (MainThread) [hass_nabucasa.iot] Received message:
2019-10-06 03:19:24 DEBUG (MainThread) [hass_nabucasa.iot] Publishing message:
So this seems like it is working fine from our end. As you can see in your pastebin, we get a discovery message from Alexa and we respond with 432 entities. Can you try to use the UI to disable most entities and just expose a couple of lights? It could very well be that 432 is too much for Alexa.
balloob
on 6 Oct 2019
👍1
Okay, did that. Left 2 lights and 2 switches and told it to sync entities.. Here's a search for Alexa.Discovery (I think my problem before was probably searching for alexa in lowercase). Unfortunately Alexa still doesn't find any new devices when I ask her.
/Alexa.Discovery
...skipping
'payload': {'directive': {'header': {'messageId': '53b19c94-19e1-4f52-a993-bddcaa4bc637',
'name': 'Discover',
'namespace': 'Alexa.Discovery',
'payloadVersion': '3'},
'payload': {'scope': {'token': '[REDACTED]',
'type': 'BearerToken'}}}}}
2019-10-06 21:28:07 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event alexa_smart_home[
L]: request=namespace=Alexa.Discovery, name=Discover, response=namespace=Alexa.Discovery, name=Di
scover.Response>
2019-10-06 21:28:07 DEBUG (MainThread) [hass_nabucasa.iot] Publishing message:
{'msgid': '7ec28009-cf04-4b70-b050-3f68524159e1',
'payload': {'event': {'header': {'messageId': '293c071e-bbd8-46f5-a28f-59dc9461f041',
'name': 'Discover.Response',
'namespace': 'Alexa.Discovery',
'payloadVersion': '3'},
'payload': {'endpoints': [{'capabilities': [{'interface': 'Alexa.PowerCont
roller',
'properties': {'proactivelyRe
ported': True,
'retrievable':
True,
'supported': [
{'name': 'powerState'}]},
'type': 'AlexaInterface',
'version': '3'},
{'interface': 'Alexa.EndpointH
ealth',
'properties': {'proactivelyRe
ported': False,
'retrievable':
True,
'supported': [
{'name': 'connectivity'}]},
'type': 'AlexaInterface',
'version': '3'}],
'cookie': {},
'description': 'switch.fibaro_system_fgs223_dou
ble_relay_switch',
'displayCategories': ['SWITCH'],
'endpointId': 'switch#fibaro_system_fgs223_doub
le_relay_switch',
'friendlyName': 'Front/Right '
'Security '
'Lights',
'manufacturerName': 'Home '
'Assistant'},
{'capabilities': [{'interface': 'Alexa.PowerCont
roller',
'properties': {'proactivelyRe
ported': True,
'retrievable':
True,
'supported': [
{'name': 'powerState'}]},
'type': 'AlexaInterface',
'version': '3'},
{'interface': 'Alexa.EndpointH
ealth',
'properties': {'proactivelyRe
ported': False,
'retrievable':
True,
'supported': [
{'name': 'connectivity'}]},
'type': 'AlexaInterface',
'version': '3'}],
'cookie': {},
'description': 'switch.fibaro_system_fgs223_dou
ble_relay_switch_2',
'displayCategories': ['SWITCH'],
'endpointId': 'switch#fibaro_system_fgs223_doub
le_relay_switch_2',
'friendlyName': 'Back/Left '
'Security '
'Lights',
'manufacturerName': 'Home '
'Assistant'},
{'capabilities': [{'interface': 'Alexa.PowerCont
roller',
'properties': {'proactivelyRe
ported': True,
'retrievable':
True,
'supported': [
{'name': 'powerState'}]},
'type': 'AlexaInterface',
'version': '3'},
{'interface': 'Alexa.Brightnes
sController',
'properties': {'proactivelyRe
ported': True,
'retrievable':
True,
'supported': [
{'name': 'brightness'}]},
'type': 'AlexaInterface',
'version': '3'},
{'interface': 'Alexa.EndpointH
ealth',
'properties': {'proactivelyRe
ported': False,
'retrievable':
True,
'supported': [
{'name': 'connectivity'}]},
'type': 'AlexaInterface',
'version': '3'}],
'cookie': {},
'description': 'light.fibaro_system_fgd212_dimm
er_2_level_2',
'displayCategories': ['LIGHT'],
'endpointId': 'light#fibaro_system_fgd212_dimme
r_2_level_2',
'friendlyName': 'FIBARO '
'System '
'FGD212 '
'Dimmer 2 '
'Level',
'manufacturerName': 'Home '
'Assistant'},
{'capabilities': [{'interface': 'Alexa.PowerCont
roller',
'properties': {'proactivelyRe
ported': True,
'retrievable':
True,
'supported': [
{'name': 'powerState'}]},
'type': 'AlexaInterface',
'version': '3'},
{'interface': 'Alexa.Brightnes
sController',
'properties': {'proactivelyRe
ported': True,
'retrievable':
True,
'supported': [
{'name': 'brightness'}]},
'type': 'AlexaInterface',
'version': '3'},
{'interface': 'Alexa.EndpointH
ealth',
'properties': {'proactivelyRe
ported': False,
'retrievable':
True,
'supported': [
{'name': 'connectivity'}]},
'type': 'AlexaInterface',
'version': '3'}],
'cookie': {},
'description': 'light.fibaro_system_fgd212_dimm
er_2_level',
'displayCategories': ['LIGHT'],
'endpointId': 'light#fibaro_system_fgd212_dimme
r_2_level',
'friendlyName': 'FIBARO '
'System '
'FGD212 '
'Dimmer 2 '
'Level',
'manufacturerName': 'Home '
'Assistant'}]}}}}
Wait, wait, I just went into the Alexa app and checked in devices and it told me that 4 were discovered!! So.. There's something to this sending in small batches.. I will try to continue a few devices at a time and see if I can get them all enabled..
Might be a good feature to add to send devices in small batches if many are selected. It's worth noting that I did have the number of devices advertised much lower like 100-200 previously so it seems the limit is somewhere between 50-150.. Probably 128 or something.
scstraus
on 6 Oct 2019
Yep, this is working. Up to 55 devices now! Thanks for the continued followup and of course for bringing us the entire freaking Homeassistant project, Paulus, it's a constant source of joy and discovery for me! It's been an honor to be helped by the man himself, though I feel slightly ashamed that I didn't think of some of this myself.
scstraus
on 6 Oct 2019
👍1
Glad it's working :-) let me know if you find an upper limit so we can update the docs !
balloob
on 7 Oct 2019
Biggest batch I tried was somewhere around 40-50.. Smallest one that failed was somewhere around 100-200, I don't really remember as I wasn't really thinking about it at the time.
scstraus
on 7 Oct 2019
Was this page helpful?
0 / 5 - 0 ratings
Related issues
sibbl
路
3Comments
coolriku
路
3Comments
moskovskiy82
路
3Comments
aweb-01
路
3Comments
missedtheapex
路
3Comments