Skip to content

Conversation

dontinelli
Copy link
Contributor

Add documentation for min/max acceptable and min/max good attributes

Proposed change

Add documentation for new extra attributes (min/max acceptable and min/max good) for the measurement sensors of fyta.

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Add documentation for min/max acceptable and min/max good attributes
@home-assistant home-assistant bot added has-parent This PR has a parent PR in another repo next This PR goes into the next branch labels Aug 13, 2025
Copy link

netlify bot commented Aug 13, 2025

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit bb28a99
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/68a2ee7cdea5de0008d42846
😎 Deploy Preview https://deploy-preview-40410--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@home-assistant home-assistant bot added the parent-merged The parent PR has been merged already label Aug 16, 2025
Copy link
Contributor

@silamon silamon left a comment

Choose a reason for hiding this comment

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

Before merging, let's resolve the comments.

@home-assistant
Copy link

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

@home-assistant home-assistant bot marked this pull request as draft August 17, 2025 09:27
@dontinelli
Copy link
Contributor Author

Before merging, let's resolve the comments.

Current wording is ok for me. @c0ffeeca7 , do you have additional comments?

@silamon
Copy link
Contributor

silamon commented Aug 17, 2025

Before merging, let's resolve the comments.

Current wording is ok for me. @c0ffeeca7 , do you have additional comments?

The comment about maximal/minimal remains open.

@dontinelli dontinelli marked this pull request as ready for review August 17, 2025 12:00
@home-assistant home-assistant bot requested a review from silamon August 17, 2025 12:01
@c0ffeeca7
Copy link
Contributor

Before merging, let's resolve the comments.

Current wording is ok for me. @c0ffeeca7 , do you have additional comments?

yes. "Maximal/minimal good". What is this? Doesn't sound like correct English. Is this what the sensor is called? What does it do?

@c0ffeeca7 c0ffeeca7 marked this pull request as draft August 18, 2025 05:58
@c0ffeeca7
Copy link
Contributor

I'm drafting this PR, as changes are needed. Please undraft it, once the changes have been implemented and the PR is ready for review again.

@dontinelli
Copy link
Contributor Author

dontinelli commented Aug 18, 2025

Before merging, let's resolve the comments.

Current wording is ok for me. @c0ffeeca7 , do you have additional comments?

yes. "Maximal/minimal good". What is this? Doesn't sound like correct English. Is this what the sensor is called? What does it do?

First off, my intent was that it is read with value, i.e. "maximal/minimal good value" and "maximal/minimal acceptable value", respectively. Agree, that this is not a very good wording (I wont comment if it is correct English and leave this for native speakers to decide), but I just had no better idea.
For the background: FYTA has several measurement sensors for plants, e.g. a temperature sensor. The thresholds now added as extra parameter represent the range where the plant feels "good" or "acceptable", respectively. So if the temperature is below the acceptable minimum, it means that it is too cold for the plant. I don't think the parameters have a huge value for the user to see, but as described in the PR can be used for automations (e.g. notifications) or the dashboard (we will use it for the fyta-plant-card).

@c0ffeeca7
Copy link
Contributor

Before merging, let's resolve the comments.

Current wording is ok for me. @c0ffeeca7 , do you have additional comments?

yes. "Maximal/minimal good". What is this? Doesn't sound like correct English. Is this what the sensor is called? What does it do?

First off, my intent was that it is read with value, i.e. "maximal/minimal good value" and "maximal/minimal acceptable value", respectively. Agree, that this is not a very good wording (I wont comment if it is correct English and leave this for native speakers to decide), but I just had no better idea. For the background: FYTA has several measurement sensors for plants, e.g. a temperature sensor. The thresholds now added as extra parameter represent the range where the plant feels "good" or "acceptable", respectively. So if the temperature is below the acceptable minimum, it means that it is too cold for the plant. I don't think the parameters have a huge value for the user to see, but as described in the PR can be used for automations (e.g. notifications) or the dashboard (we will use it for the fyta-plant-card).

Does it mean "Best/worst value for the plant"?

@dontinelli
Copy link
Contributor Author

No, not best worst. It's a range. Let's say you have a Banana that likes it warm. So below 10 it's too cold, that could be min acceptable. 15 could be min good. Between 15 and 30 is perfect. 30 would be max good and probably 35 would be max acceptable. Above 35 it's too hot.

@c0ffeeca7
Copy link
Contributor

No, not best worst. It's a range. Let's say you have a Banana that likes it warm. So below 10 it's too cold, that could be min acceptable. 15 could be min good. Between 15 and 30 is perfect. 30 would be max good and probably 35 would be max
acceptable. Above 35 it's too hot.

Ok, so maybe something like this to give a bit more context?
For the measurement sensors (light, moisture, salinity, and temperature), the maximal/minimal values that define the ranges of what is considered acceptable and good for the plant are saved as an extra attribute of the sensor. For example: Below 10 it's too cold, that could be the minimum acceptable. 15 could be the minimum of the good range. Between 15 and 30 is perfect. 30 would be maximum good and 35 would be the maximum acceptable. Above 35 it's too hot. These values can be used for automations or visualizations on the dashboard.

@dontinelli dontinelli marked this pull request as ready for review August 18, 2025 09:12
Copy link
Contributor

@c0ffeeca7 c0ffeeca7 left a comment

Choose a reason for hiding this comment

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

Thank you, @dontinelli 👍

@c0ffeeca7 c0ffeeca7 dismissed silamon’s stale review August 18, 2025 09:15

requested changes have been implemented.

@c0ffeeca7 c0ffeeca7 enabled auto-merge (squash) August 18, 2025 09:15
@c0ffeeca7 c0ffeeca7 merged commit 2a96ef1 into home-assistant:next Aug 18, 2025
7 checks passed
@home-assistant home-assistant bot removed the parent-merged The parent PR has been merged already label Aug 18, 2025
@dontinelli dontinelli deleted the patch-2 branch August 18, 2025 09:23
@github-actions github-actions bot locked and limited conversation to collaborators Aug 19, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
has-parent This PR has a parent PR in another repo next This PR goes into the next branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants