search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
72.45k stars 30.33k forks source link

homematic component ERROR in Logfile - "No entity id specified for entity {}".format(self.name)) #7080

Closed leinich closed 7 years ago

leinich commented 7 years ago

Component/platform: component homematic Reproducable in home-assistant 0.40 , 0.41, 0.42, 0.42.3

Description of problem: The below error are written regulary to the logfile for the homeatic devices: HM-ES-PMSw1-Pl I can see all 5 expected sensors, which are: sensor.XXXXXXXXX_current sensor.XXXXXXXXX_energy_counter sensor.XXXXXXXXX_power sensor.XXXXXXXXX_voltage switch.XXXXXXXXX

Expected: I don't notice any issues while using the devices.

Traceback (if applicable): Note: replaced the device serial number with XXXXXXXXX

17-04-12 17:34:40 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step
    result = next(coro)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 204, in async_update_ha_state
    "No entity id specified for entity {}".format(self.name))
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity XXXXXXXXX
17-04-12 17:34:40 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step
    result = next(coro)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 204, in async_update_ha_state
    "No entity id specified for entity {}".format(self.name))
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity XXXXXXXXX
17-04-12 17:34:40 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step
    result = next(coro)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 204, in async_update_ha_state
    "No entity id specified for entity {}".format(self.name))
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity XXXXXXXXX
17-04-12 17:34:40 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 237, in _step
    result = next(coro)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 204, in async_update_ha_state
    "No entity id specified for entity {}".format(self.name))
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity XXXXXXXXX
17-04-12 17:35:43 ERROR (Thread-1) [pyhomematic.devicetypes.generic] HMGeneric.getValue: POWER on XXXXXXXXX:2 Exception: <Fault -1: 'Failure'>
17-04-12 17:35:46 ERROR (Thread-1) [pyhomematic.devicetypes.generic] HMGeneric.getValue: VOLTAGE on XXXXXXXXX:2 Exception: <Fault -1: 'Failure'>
17-04-12 17:35:50 ERROR (Thread-1) [pyhomematic.devicetypes.generic] HMGeneric.getValue: CURRENT on XXXXXXXXX:2 Exception: <Fault -1: 'Failure'>
17-04-12 17:35:53 ERROR (Thread-1) [pyhomematic.devicetypes.generic] HMGeneric.getValue: ENERGY_COUNTER on XXXXXXXXX:2 Exception: <Fault -1: 'Failure'>

Additional info: If you need any additional information, please let me know.

danielperna84 commented 7 years ago

By "regularily" you mean these messages keep popping up during runtime? The last four lines in some cases are normal. I have a HM-ES-TX-WM with the LED-sensor attached. When starting HASS, the Gas-Sensor parameters are queried, even though the device is not configured to have any values there. Hence the errors. But these values only get queried manually once on startup. In your case the getValue method is called. Which, as stated above, usually only happens on startup. Do you have any automations that somehow manually try to get some of these values? On top of that I have never seen all those exceptions you have. I'm still on 0.41 though, so maybe these exceptions are a result of 0.42.

leinich commented 7 years ago

With regularly I mean every time I restart HA. I never noticed any ERROR during runtime. As I have several devices from type HM-ES-PMSw1-Pl and HM-ES-TX-WM for each device multiple error log line are written. Every restart produces around 80 lines of error in the logfile like above. No currently I don't have any automation i place using any HM-ES-PMSw1-Pl or HM-ES-TX-WM.

danielperna84 commented 7 years ago

In that case what you're experiencing is the same issue as mine, which is not a bug. What happens is that during the setup HASS asks the device for the values of all available values that are theoretically available. The avilability of those values depends on the configuration / state of the device, which is why not all values are present at any time. In terms of logging we rate those situations as errors, because it could actually be a severe error causing this behaviour. In the context of a HASS restart though it's no problem at all.

balloobbot commented 7 years ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.

Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment :+1:

balloobbot commented 7 years ago

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍