The problem Since not too long I am getting several times a day wa

Hey there <a class="user-mention notranslate" data-hovercard-type="user" data-hovercar

Also got this in my logs after restart. <div class="snippet-clipboard-content notr

<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Recently getting several times a day warning messages of evohome connection problems ,about home-assistant/core

Comments (7)

zxdavb commented on July 23, 2024 1

This is now a support issue (IMO, there is nothing wrong with the evohome integration) - please ask for help in the community forum.

from core.

home-assistant commented on July 23, 2024

Hey there @zxdavb, mind taking a look at this issue as it has been labeled with an integration (evohome) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of evohome can trigger bot actions by commenting:

@home-assistant close Closes the issue.
@home-assistant rename Awesome new title Renames the issue.
@home-assistant reopen Reopen the issue.
@home-assistant unassign evohome Removes the current integration label and assignees on the issue, add the integration domain after the command.
@home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
@home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

evohome documentation
evohome source
_{^{(message by IssueLinks)}}

from core.

smarthomefamilyverrips commented on July 23, 2024

Also got this in my logs after restart.

Logger: homeassistant.setup
Source: setup.py:404
First occurred: 12:00:53 (1 occurrences)
Last logged: 12:00:53

Error during setup of component evohome
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1025, in _wrap_create_connection
    return await self._loop.create_connection(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1147, in create_connection
    transport, protocol = await self._create_connection_transport(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1180, in _create_connection_transport
    await waiter
  File "/usr/local/lib/python3.12/asyncio/selector_events.py", line 978, in _read_ready__get_buffer
    nbytes = self._sock.recv_into(buf)
             ^^^^^^^^^^^^^^^^^^^^^^^^^
ConnectionResetError: [Errno 104] Connection reset by peer

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/evohomeasync2/broker.py", line 231, in get
    response, content = await self._client(  # type: ignore[assignment]
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/evohomeasync2/broker.py", line 116, in _client
    async with _session_method(url, **kwargs) as response:  # type: ignore[arg-type]
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 1197, in __aenter__
    self._resp = await self._coro
                 ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client.py", line 581, in _request
    conn = await self._connector.connect(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 544, in connect
    proto = await self._create_connection(req, traces, timeout)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 944, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1257, in _create_direct_connection
    raise last_exc
  File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1226, in _create_direct_connection
    transp, proto = await self._wrap_create_connection(
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/connector.py", line 1033, in _wrap_create_connection
    raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host tccna.honeywell.com:443 ssl:default [Connection reset by peer]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 404, in _async_setup_component
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/evohome/__init__.py", line 244, in async_setup
    await client_v2.login()
  File "/usr/local/lib/python3.12/site-packages/evohomeasync2/base.py", line 172, in login
    await self.user_account()
  File "/usr/local/lib/python3.12/site-packages/evohomeasync2/base.py", line 205, in user_account
    self._user_account = await self.broker.get(
                         ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/evohomeasync2/broker.py", line 242, in get
    raise exc.RequestFailed(str(err)) from err
evohomeasync2.exceptions.RequestFailed: Cannot connect to host tccna.honeywell.com:443 ssl:default [Connection reset by peer]

from core.

zxdavb commented on July 23, 2024

evohomeasync2.exceptions.RequestFailed: 
Cannot connect to host tccna.honeywell.com:443 ssl:default [Connection reset by peer]

The evohome integration is simply reporting a fault it has encountered. It is not the cause of that fault.

In this case, the connection has been reset by the peer (tccna.honeywell.com).

from core.

zxdavb commented on July 23, 2024

If you look at: https://status.resideo.com, in this instance, it has a message:

Investigating - We are aware some of our customers are experiencing issues with our TCC application

However, I don't know if that is the specific cause of your issue.

from core.

smarthomefamilyverrips commented on July 23, 2024

@zxdavb OK thank you, just wanted to report as it started since a few days also ehen where no issues reportedby the Resido status site. But will keep a eye on the Resido status site and see if messages keep popping up in system logs.

from core.

smarthomefamilyverrips commented on July 23, 2024

@zxdavb I still get daily these errors but there are no issues reported on the resideo website for last few days. If I recall correctly this actually started after the issue there was 1.5 - 2 weeks ago when there was a big outage of TCC and also the TCC app not worked, is it possible they did made some changes regarding connection to the TCC making it more sensitive for failing to connect?

from core.

Recently getting several times a day warning messages of evohome connection problems about core HOT 7 CLOSED

Comments (7)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent