Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Another 2021.2.0b1 headsup: Error adding entities for domain binary_sensor with platform blueiris #100

Closed
BoneheadFraggle opened this issue Jan 31, 2021 · 2 comments

Comments

@BoneheadFraggle
Copy link

Last known working HA version: 2021.1.5

Now running HA 2021.2.0b1 + BlueIris NVR 1.0.1:
I have two of those in the logs after every restart. I can't figure out which binary_sensor it refers to.

2021-01-31 09:57:01 ERROR (MainThread) [homeassistant.components.binary_sensor] Error adding entities for domain binary_sensor with platform blueiris
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 315, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 506, in _async_add_entity
    await entity.add_to_platform_finish()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 530, in add_to_platform_finish
    await self.async_added_to_hass()
  File "/config/custom_components/blueiris/models/base_entity.py", line 102, in async_added_to_hass
    await self.async_added_to_hass_local()
  File "/config/custom_components/blueiris/binary_sensors/main.py", line 40, in async_added_to_hass_local
    f"Subscribing to MQTT topics '{MQTT_ALL_TOPIC}', QOS: {DEFAULT_QOS}"
NameError: name 'DEFAULT_QOS' is not defined

96 binary_sensors are created;
five binary sensors per camera (audio, connectivity, dio, external, motion) x 19 cameras = 95 sensors.
95 + "binary_sensor.blueiris_alerts" = 96.
Read the documentation and that seems to be correct.

I'd be glad to provide more info.

@FuzzyMistborn
Copy link

Seeing this on 2021.1.x when running v. 1.0.1 of the component so it's not related to the beta. Rolling back to 1.0 for now as this bug seems to kill any alerts.

@elad-bar
Copy link
Owner

Will fix it later today

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants