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

Fix WLED link + explain about segments #2240

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

igorsantos07
Copy link
Contributor

Also makes it clearer how to find WLED on the configuration GUI.

P.S.: should segmented WLEDs also be found automatically by the integration? In my case, it only found a single WLED strip, but the other which was segmented got ignored, and I had to enable it manually (although it also had the brightness limiter off, but I let it rest a few days after enabling that option, to check if the integration would pick it up at some point, but it didn't).

Also makes it clearer how to find WLED on the configuration GUI.

.. important::
The brightness limiter must be turned on in WLED for this to work! Otherwise WLED will not provide an estimated current.

You can setup sensors both with YAML or GUI.
When you use the GUI select :guilabel:`wled` in the calculation_strategy dropdown.
When you use the GUI, select the "Virtual power (manual)" sensor type, and :guilabel:`wled` in the "Calculation strategy" dropdown.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When you use the GUI, select the "Virtual power (manual)" sensor type, and :guilabel:`wled` in the "Calculation strategy" dropdown.
When you use the GUI, select the :guilabel:`Virtual power (manual)` sensor type, and :guilabel:`wled` in the "Calculation strategy" dropdown.

This will represent it nicely formatted.


.. important::
The brightness limiter must be turned on in WLED for this to work! Otherwise WLED will not provide an estimated current.

You can setup sensors both with YAML or GUI.
When you use the GUI select :guilabel:`wled` in the calculation_strategy dropdown.
When you use the GUI, select the "Virtual power (manual)" sensor type, and :guilabel:`wled` in the "Calculation strategy" dropdown.
If you have multiple segments, select any of them as the source entity; selecting a helper group with all segments will cause a failure to find the current sensor, even if entity IDs match perfectly.
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think power sensor per segment will work correctly, as there is no estimated_current sensor supplied per segment by the WLED integration as far as I know.
So we might need to add a note that WLED strategy cannot be used for segments unfortunately.

@bramstroker
Copy link
Owner

Also makes it clearer how to find WLED on the configuration GUI.

P.S.: should segmented WLEDs also be found automatically by the integration? In my case, it only found a single WLED strip, but the other which was segmented got ignored, and I had to enable it manually (although it also had the brightness limiter off, but I let it rest a few days after enabling that option, to check if the integration would pick it up at some point, but it didn't).

In the discovery routine of powercalc only the main wled light is considered. master and segment* are deliberately excluded as there is no estimated_current entity per segment in WLED integration.
https://github.com/bramstroker/homeassistant-powercalc/blob/master/custom_components/powercalc/discovery.py#L174

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

Successfully merging this pull request may close these issues.

None yet

2 participants