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

Simulated brightness entity doesn't appear in Home Assistant #13981

Closed
YodaDaCoda opened this issue Sep 12, 2022 · 8 comments
Closed

Simulated brightness entity doesn't appear in Home Assistant #13981

YodaDaCoda opened this issue Sep 12, 2022 · 8 comments
Labels
problem Something isn't working stale Stale issues

Comments

@YodaDaCoda
Copy link

What happened?

I set up simulated_brightness on my E1744 & observed the brightness attribute changing via the State tab in the webui as I turned the remote. I went to Home Assistant to use the new brightness on an automation and couldn't find it.

What did you expect to happen?

I expected to find a brightness entity attached to the device in Home Assistant.

How to reproduce it (minimal and precise)

Pair E1744 device. Observe it is added to Home assistant. Configure simulated_brightness in z2m. Observe the brightness changes within the state as the remote is rotated. Note the brightness does not appear in Home Assistant.

Zigbee2MQTT version

1.27.2

Adapter firmware version

20220219

Adapter

zzh!

Debug log

log.txt

@YodaDaCoda YodaDaCoda added the problem Something isn't working label Sep 12, 2022
@ModuCZ
Copy link

ModuCZ commented Sep 24, 2022

I have experienced the same issue. Brightness value is visible in MQTT Info inside HA.

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Oct 25, 2022
@YodaDaCoda
Copy link
Author

Issue persists.

@github-actions github-actions bot removed the stale Stale issues label Nov 1, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2022

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the stale Stale issues label Dec 2, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 9, 2022
@AndreKR
Copy link

AndreKR commented Dec 30, 2022

The issue is still valid.

@harristom
Copy link

I have a brightness attribute in the volume action sensor

@thefelixno
Copy link

had to activate legacy entity attributes for the ha-integrations, now works for me

homeassistant:
  # Optional: Home Assistant legacy entity attributes, (default: shown below), when enabled:
  # Zigbee2MQTT will send additional states as attributes with each entity. For example,
  # A temperature & humidity sensor will have 2 entities for the temperature and
  # humidity, with this setting enabled both entities will also have
  # an temperature and humidity attribute.
  # Note: Disabling this option, requires a Home Assistant restart
  legacy_entity_attributes: true

@rrakso
Copy link

rrakso commented Jul 24, 2024

I can confirm this. I had (somehow) set legacy_entity_attributes to false, when changed to true it works very well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working stale Stale issues
Projects
None yet
Development

No branches or pull requests

6 participants