Log error: NoEntitySpecifiedError

I keep getting this in my log:

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/helpers/entity.py”, line 199, in async_update_ha_state
“No entity id specified for entity {}”.format(self.name))
homeassistant.exceptions.NoEntitySpecifiedError: No entity id specified for entity Door Open

relevant section from my configuration.yaml:

binary_sensor:
  - platform: gc100
    ports:
      '4:1': Doorbell
      '4:2': Door Open
      '5:2': Upstairs Rear Window Open

Why would there be no such errors for Doorbell or Upstairs Rear Window Open?

(I am the developer for gc100 so if this should be moved under the developer section in the forum that’s fine)

1 Like

Did you find any solution? I keep getting these since at least a month ago, but I can’t see that there is anything wrong. All works just fine so I don’t give it much thought, but my log file is full of these errors.

Kjell

I’ve not found any solution, and like you it’s been working so I haven’t spent much time on it.

Are you also using the gc100 platform, or are you getting these errors for another platform?

I’m using Rpi3, upgraded to HassOS.
But I had these errors before when I was running the old ResinOS.
Anoying…

Ah, now I see. gc100 is a system to send RS232 and IR. I thought you was talking about a mainboard of some sort upon which you were running HA :slight_smile:

As of today, I now seem to be getting this same error, but again, doesn’t appear to be affecting anything.

For me it’s on GPIO, not GC100, but still a binary sensor, so I think it’s related?

Up until today, I had 13 GPIO pins in use, no errors. Today I connected a 14th device (pin 5) and suddenly that one device, and no others, are throwing this error.

Everything about it is the same as the existing devices which had no issues. If you have any ideas, I’m all ears!

1 Like

Hi David, I know this post is reallllly old but i’m also trying to bind my doorbell to my HASS and getting the same error.

Have you found a fix ?

No sorry, I abandoned the gc-100 and got a Reolink poe doorbell which has been working fine.