Esphome shows unavailable but Online in ESPHome GUI

olddawgpowers · August 19, 2019, 7:22am

Only a few weeks into Home Assistant. I have two identical Esphome Garage Door openers that have been working flawless for a couple of weeks. One no longer works. It shows Online in the GUI but unavailable in Developer Tools States. When I compare the logs from the Show Log on the GUI they look the same except when I trigger the working one it shows (in blue). My Signal strength: -79 dB is a little worse on the one that is not working.
I am using DHCP Reservation and both have the correct reserved IP addresses. I am using HiLetgo ESP8266 NodeMCU LUA CP2102 ESP-12E. I believe I picked NodeMCU as the Device Type. In the yaml file it shows board: nodemcuv2.

bvansambeek · July 30, 2020, 8:00pm

github.com/esphome/issues

ESPhome devices online but no connection to HASS?

opened 12:19PM - 28 Aug 19 UTC

closed 01:14PM - 28 Aug 19 UTC

voydz

good first issue Connection Issue

**Operating environment/Installation (Hass.io/Docker/pip/etc.):**  hass.io running on a Debian 9 VM **ESP (ESP32/ESP8266, Board/Sonoff):**  The issue affects one of two exactly the same NodeMCU (lolin) + DHT22 configurations and one out of one Shelly 2.5 device. See YAML config below. **Affected component:**  As far as I can tell, the issue might be related to the `api:` component. **Description of problem:** After running weeks without issues after updating to hass 0.97.2 I noticed a few of my ESPhome devices appeared to be offline. I checked my network configuration and found no problems. I checked the dashboard of the ESPhome addon. All my ESPhome devices are booting up, are displayed as online and spitting out logs OTA just fine. From ESPhome side of things, all seems fine, no issues logged there. But home assistant is not able to get sensor values for **some** of my devices. Those are displayed as "disconnected" by the `binary_sensor:` status platform. Every sensor and switch affected is "unavailable". So the strange thing is, I got two other devices with binary_sensors, working just fine. One is an exact clone of the sensor02 device (see YAML config below), which started working after unplugging it for a longer period of time. (Nope, this was not working for the other two.) And I got one RGB Controller D1mini which does not seem to be affected at all. Never needed to restart it or something. [Here are some screenshots](https://imgur.com/a/VWopuCP) The most absurd thing is, I am not getting any valuable log information, where the problem may be coming from. (see logs below) **Problem-relevant YAML-configuration entries:** ### .config.yaml ```yaml wifi: ssid: !secret wifi_ssid password: !secret wifi_psk # Enable logging logger: # Enable Home Assistant API api: password: !secret api_pw ota: password: !secret api_pw ``` ### workroom_switch01.yaml (Shelly 2.5) ```yaml esphome: name: workroom_switch01 platform: ESP8266 board: esp01_1m <<: !include .config.yaml sensor: - platform: uptime name: "workroom_switch01_uptime" update_interval: 60s - platform: wifi_signal name: "workroom_switch01_wifi" update_interval: 60s text_sensor: - platform: version name: "workroom_switch01_version" binary_sensor: - platform: status name: "workroom_switch01_status" - platform: gpio pin: number: GPIO5 name: "workroom_wallswitch_right" - platform: gpio pin: number: GPIO13 name: "workroom_wallswitch_left" output: - platform: gpio pin: GPIO4 id: relay_1 - platform: gpio pin: GPIO15 id: relay_2 light: - platform: binary name: "workroom_ceiling_light_1" output: relay_1 - platform: binary name: "workroom_ceiling_light_2" output: relay_2 ``` ### sensor02.yaml (Simple NodeMCU + DHT22) ```yaml esphome: name: sensor02 platform: ESP8266 board: nodemcuv2 <<: !include .config.yaml sensor: - platform: dht pin: D5 model: DHT22 temperature: name: "livingroom_sensor_temperature" humidity: name: "livingroom_sensor_humidity" update_interval: 60s - platform: uptime name: "sensor02_uptime" update_interval: 60s - platform: wifi_signal name: "sensor02_wifi" update_interval: 60s text_sensor: - platform: version name: "sensor02_version" binary_sensor: - platform: status name: "sensor02_status" ``` **Logs (if applicable):**  (notice, these are from hass) I am seeing this from time to time, not sure if it is connected to sort of a communication issue: ``` Unhandled exception Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.py", line 448, in start await resp.write_eof() File "/usr/local/lib/python3.7/site-packages/aiohttp/web_response.py", line 444, in write_eof await self._payload_writer.write_eof(data) File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 138, in write_eof self._write(chunk) File "/usr/local/lib/python3.7/site-packages/aiohttp/http_writer.py", line 67, in _write raise ConnectionResetError('Cannot write to closing transport') ConnectionResetError: Cannot write to closing transport ``` **EDIT:** I noticed this error log below might come from adding the same ESPhome device two times therefore clashing entity_id's. I keep the log for reference. ``` Error doing job: Task exception was never retrieved Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/core.py", line 673, in _async_remove_listener self._listeners[event_type].remove(listener) File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 504, in __eq__ if self.unique_id is None or other.unique_id is None: File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 548, in unique_id if not self._static_info.unique_id: File "/usr/src/homeassistant/homeassistant/components/esphome/binary_sensor.py", line 32, in _static_info return super()._static_info File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 516, in _static_info return self._entry_data.info[self._component_key][self._key] File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 512, in _entry_data return self.hass.data[DATA_KEY][self._entry_id] KeyError: 'f09efc14f0734df585c5d04704685864' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 426, in async_remove_entity await self.entities[entity_id].async_remove() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 441, in async_remove self._on_remove.pop()() File "/usr/src/homeassistant/homeassistant/core.py", line 616, in remove_listener self._async_remove_listener(event_type, listener) File "/usr/src/homeassistant/homeassistant/core.py", line 681, in _async_remove_listener _LOGGER.warning("Unable to remove unknown listener %s", listener) File "/usr/local/lib/python3.7/logging/__init__.py", line 1390, in warning self._log(WARNING, msg, args, **kwargs) File "/usr/local/lib/python3.7/logging/__init__.py", line 1514, in _log self.handle(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 1524, in handle self.callHandlers(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 1586, in callHandlers hdlr.handle(record) File "/usr/local/lib/python3.7/logging/__init__.py", line 894, in handle self.emit(record) File "/usr/src/homeassistant/homeassistant/components/system_log/__init__.py", line 176, in emit record, stack, _figure_out_source(record, stack, self.hass) File "/usr/src/homeassistant/homeassistant/components/system_log/__init__.py", line 102, in __init__ self.message = record.getMessage() File "/usr/local/lib/python3.7/logging/__init__.py", line 369, in getMessage msg = msg % self.args File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 519, in __repr__ return "<Entity {}: {}>".format(self.name, self.state) File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 562, in name return self._static_info.name File "/usr/src/homeassistant/homeassistant/components/esphome/binary_sensor.py", line 32, in _static_info return super()._static_info File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 516, in _static_info return self._entry_data.info[self._component_key][self._key] File "/usr/src/homeassistant/homeassistant/components/esphome/__init__.py", line 512, in _entry_data return self.hass.data[DATA_KEY][self._entry_id] KeyError: 'f09efc14f0734df585c5d04704685864' ``` **Additional information and things you've tried:** * checked network configuration * readded devices as hass esphome integration

How to Fix

Delete the old ESPhome integration in home-assistant

Readd the ESPhome integration using <devicename>.local or a static ip (see esphome docs for this)

Restart home-assistant

Make sure the entity_ids match or adjust them in the integration config in home-assistant

Merlin · September 9, 2020, 1:00am

I don’t understand step 2 here. Does anyone have insight into what it means to “read the esphome integration using .local?” I don’t see anything like this in the ESPHome docs.

Any assistance is greatly appreciated.

Which of these is the entity ID?

INFO Reading configuration /config/esphome/gas_woodstove.yaml...
INFO Starting log output from gas_woodstove.local using esphome API
INFO Connecting to gas_woodstove.local:6053 (192.168.1.6)
INFO Successfully connected to gas_woodstove.local
[18:50:35][I][app:100]: ESPHome version 1.14.4 compiled on Sep  5 2020, 13:27:58
[18:50:35][C][status_led:019]: Status LED:
[18:50:35][C][status_led:020]:   Pin: GPIO13 (Mode: OUTPUT, INVERTED)
[18:50:35][C][wifi:415]: WiFi:
[18:50:35][C][wifi:283]:   SSID: 

[redacted]
[18:50:35][C][wifi:284]:   IP Address: 192.168.1.6
[18:50:35][C][wifi:286]:   BSSID: 

[redacted]
[18:50:35][C][wifi:287]:   Hostname: 'gas_woodstove'
[18:50:35][C][wifi:291]:   Signal strength: -60 dB ▂▄▆█
[18:50:35][C][wifi:295]:   Channel: 6
[18:50:35][C][wifi:296]:   Subnet: 255.255.255.0
[18:50:35][C][wifi:297]:   Gateway: 192.168.1.1
[18:50:35][C][wifi:298]:   DNS1: 192.168.1.1
[18:50:35][C][wifi:299]:   DNS2: (IP unset)
[18:50:35][C][gpio.binary_sensor:015]: GPIO Binary Sensor 'Gas Stove Button'
[18:50:35][C][gpio.binary_sensor:016]:   Pin: GPIO0 (Mode: INPUT_PULLUP, INVERTED)
[18:50:35][C][switch.gpio:042]: GPIO Switch 'Gas Stove'
[18:50:35][C][switch.gpio:043]:   Pin: GPIO12 (Mode: OUTPUT)
[18:50:35][C][switch.gpio:059]:   Restore Mode: Restore (Defaults to OFF)
[18:50:35][C][logger:175]: Logger:
[18:50:35][C][logger:176]:   Level: DEBUG
[18:50:35][C][logger:177]:   Log Baud Rate: 115200
[18:50:35][C][logger:178]:   Hardware UART: UART0
[18:50:35][C][captive_portal:169]: Captive Portal:
[18:50:35][C][ota:029]: Over-The-Air Updates:
[18:50:35][C][ota:030]:   Address: gas_woodstove.local:8266
[18:50:35][C][api:095]: API Server:
[18:50:35][C][api:096]:   Address: gas_woodstove.local:6053

bvansambeek · April 5, 2022, 2:49pm

Hi @Merlin I did not see this message until now. You should have tagged me or use reply.
You probably fixed this or abandoned it, however for other people:
Step 2 was rewritten into: Readd the ESPhome integration using .local or a static ip (see esphome docs for this)
Step 2 breaks down to:

You should check what the device name is in ESPhome, in your case “gas_woodstove”.
Go to: Home Assistant configuration - Devices & Services - hit button “+ ADD INTEGRATION”
Search and select ESPHome
under Host fill in “.local” in your case “gas_woodstove.local”

Although this does not happen anymore to me with current versions, so might be fixed somewhere…

Joe3 · August 17, 2022, 10:08am

One online only a few left to go.

All of these are actually online but for quite a few updates now they never show online.

bvansambeek Bouwy s how to fix seems to work but why is this needed?

bvansambeek · September 9, 2022, 9:45am

Might be related to the advise not to use underscores.

github.com/esphome/esphome

Warn if underscore character is used in hostname

esphome:dev ← davet2001:block_underscore_in_name

opened 10:04PM - 27 Jul 21 UTC

davet2001

+34 -3

# What does this implement/fix? Warns about underscores in hostnames to preven…t DHCP/DNS problems. - Underscores in device names can cause strange DNS problems that are hard for users to trace, [example1](https://github.com/esphome/issues/issues/1123), [example2](https://community.home-assistant.io/t/nodes-created-from-esphome-not-showing-a-entities-in-home-assist/228807). - According to [RFC1912](https://datatracker.ietf.org/doc/html/rfc1912), underscores are not allowed in hostnames. This PR causes the compile to raise an warning when the user tries to use an underscore in a hostname. It is not a breaking change because it is just a warning. If the user choose to rename, they will have to remove & re-add the device in HA, the warning links to instructions. ## Types of changes - [x] Bugfix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [x] Other **Related issue or feature (if applicable):** Partial fix for https://github.com/esphome/issues/issues/1123 **Pull request in [esphome-docs](https://github.com/esphome/esphome-docs) with documentation (if applicable):** https://github.com/esphome/esphome-docs/pull/1366 ## Test Environment - [ ] ESP32 - [ ] ESP8266 ## Checklist: - [X] The code change is tested and works locally. - [X] Tests have been added to verify that the new code works (under `tests/` folder). If user exposed functionality or configuration variables are added/changed: - [x] Documentation added/updated in [esphome-docs](https://github.com/esphome/esphome-docs). (The [documentation](https://esphome.io/components/esphome.html#configuration-variables) is already correct as it does not state that underscores are allowed)

zioCristia · July 7, 2023, 8:31am

I’m having this same problem with a device, “unavailable” in HA but online in EspHome.

It’s not the first time and I always menage to re-add them back. But now with the new Home Assistant update, which reorganise the “Devices & Services” window I’m not able to remove the old ESPHome integration because the device appears under the window “Devices” but not in the list of the EspHome devices which actually allows to manage the devices.

I’ve tried to add the integration as @bvansambeek suggests but it says “device already configured”.

The funny thing is that the temperature sensor is still working properly and sending regularly the data.

Any suggestion on what to do?