Skip to content

Commit b420475

Browse files
committed
update: Conditional entities, Core 2025.10.1 fix, various other fixes
1 parent 1b0af6f commit b420475

36 files changed

Lines changed: 5729 additions & 2838 deletions

.github/CODE_OF_CONDUCT.md

Lines changed: 38 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,38 @@
1-
# Code of Conduct
2-
3-
Welcome to the **Monitor My Solar** repository! To create a collaborative and productive environment, we ask that all contributors and users adhere to the following guidelines.
4-
5-
## 1. Respect and Courtesy
6-
7-
We are committed to providing a friendly, safe, and welcoming environment for everyone. Please treat others with respect and courtesy, and use welcoming and inclusive language.
8-
9-
## 2. Search Issues Before Posting
10-
11-
Before opening a new issue, **please check the existing issues** to see if your question or problem has already been reported. Duplicate issues can clutter the tracker and make it difficult to focus on current issues. If your issue is similar to an existing one, feel free to add a comment instead of opening a new issue.
12-
13-
## 3. Issue and Pull Request Guidelines
14-
15-
- **Issues**: Provide a clear and concise description of the problem, steps to reproduce, and any relevant screenshots or error messages. Make sure to use appropriate labels if applicable.
16-
- **Pull Requests**: Ensure that your pull request includes a **detailed description** of the changes you are making. If it addresses an issue, reference the issue number. Describe the purpose of the feature or bug fix and provide any relevant context.
17-
18-
## 4. License Compliance
19-
20-
By contributing to this repository, you agree that all code is subject to the terms of our [LICENSE](../LICENSE). Ensure that your contributions do not include unlicensed or incompatible code from third-party sources. Respect the license terms for any code, dependencies, or resources included in your contributions.
21-
22-
## 5. Constructive Feedback and Reviews
23-
24-
When reviewing others’ contributions, focus on providing **constructive feedback**. Be clear, specific, and kind in your suggestions. If you receive feedback, consider it thoughtfully and respond courteously.
25-
26-
## 6. Reporting Issues
27-
28-
If you observe any behavior that violates this Code of Conduct or makes you feel uncomfortable, please report it by contacting the repository maintainers. We are committed to addressing and resolving all issues fairly and promptly.
29-
30-
## 7. Consequences
31-
32-
Failure to adhere to this Code of Conduct may result in actions ranging from warnings to more severe consequences, such as temporary or permanent restrictions on participation in the repository.
33-
34-
## 8. Contact
35-
36-
For questions or concerns about this Code of Conduct, please reach out to the repository maintainers directly.
37-
38-
Thank you for contributing to a positive and productive community!
1+
# Code of Conduct
2+
3+
Welcome to the **Monitor My Solar** repository! To create a collaborative and productive environment, we ask that all contributors and users adhere to the following guidelines.
4+
5+
## 1. Respect and Courtesy
6+
7+
We are committed to providing a friendly, safe, and welcoming environment for everyone. Please treat others with respect and courtesy, and use welcoming and inclusive language.
8+
9+
## 2. Search Issues Before Posting
10+
11+
Before opening a new issue, **please check the existing issues** to see if your question or problem has already been reported. Duplicate issues can clutter the tracker and make it difficult to focus on current issues. If your issue is similar to an existing one, feel free to add a comment instead of opening a new issue.
12+
13+
## 3. Issue and Pull Request Guidelines
14+
15+
- **Issues**: Provide a clear and concise description of the problem, steps to reproduce, and any relevant screenshots or error messages. Make sure to use appropriate labels if applicable.
16+
- **Pull Requests**: Ensure that your pull request includes a **detailed description** of the changes you are making. If it addresses an issue, reference the issue number. Describe the purpose of the feature or bug fix and provide any relevant context.
17+
18+
## 4. License Compliance
19+
20+
By contributing to this repository, you agree that all code is subject to the terms of our [LICENSE](../LICENSE). Ensure that your contributions do not include unlicensed or incompatible code from third-party sources. Respect the license terms for any code, dependencies, or resources included in your contributions.
21+
22+
## 5. Constructive Feedback and Reviews
23+
24+
When reviewing others’ contributions, focus on providing **constructive feedback**. Be clear, specific, and kind in your suggestions. If you receive feedback, consider it thoughtfully and respond courteously.
25+
26+
## 6. Reporting Issues
27+
28+
If you observe any behavior that violates this Code of Conduct or makes you feel uncomfortable, please report it by contacting the repository maintainers. We are committed to addressing and resolving all issues fairly and promptly.
29+
30+
## 7. Consequences
31+
32+
Failure to adhere to this Code of Conduct may result in actions ranging from warnings to more severe consequences, such as temporary or permanent restrictions on participation in the repository.
33+
34+
## 8. Contact
35+
36+
For questions or concerns about this Code of Conduct, please reach out to the repository maintainers directly.
37+
38+
Thank you for contributing to a positive and productive community!
Lines changed: 70 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -1,70 +1,70 @@
1-
name: Bug Report
2-
description: Report an issue with the dongle, Home Assistant, or web monitoring.
3-
title: "[BUG] Brief description of the issue"
4-
labels: ["bug"]
5-
6-
body:
7-
- type: dropdown
8-
id: component
9-
attributes:
10-
label: "Affected Component"
11-
description: "Select the component related to your issue."
12-
options:
13-
- Dongle
14-
- Home Assistant
15-
- Web Monitoring
16-
validations:
17-
required: true
18-
19-
- type: input
20-
id: version
21-
attributes:
22-
label: "Version Information"
23-
description: "Enter the version of the integration or dongle firmware. Type N/A if related to Web Monitoring."
24-
placeholder: "Enter version here"
25-
validations:
26-
required: true
27-
28-
- type: textarea
29-
id: images_videos
30-
attributes:
31-
label: "Media Attachments"
32-
description: "Provide links to any images or videos showing the issue, if applicable."
33-
placeholder: "Paste links to images or videos here"
34-
validations:
35-
required: true
36-
37-
- type: textarea
38-
id: mqtt_output
39-
attributes:
40-
label: "MQTT Output"
41-
description: "If the issue relates to the Dongle, Home Assistant, or Web Monitoring, provide the MQTT output from `dongleID/status`."
42-
placeholder: "Paste MQTT output here"
43-
render: shell
44-
validations:
45-
required: true
46-
47-
- type: textarea
48-
id: detailed_description
49-
attributes:
50-
label: "Detailed Description"
51-
description: "Provide a detailed description of the issue, including steps to reproduce and the expected behavior."
52-
placeholder: "Describe the issue in detail"
53-
validations:
54-
required: true
55-
- type: checkboxes
56-
id: issue_check
57-
attributes:
58-
label: Issues
59-
description: By Submitting this Issue you confirm you have checked to see if the issue already exists and your not duplicating the bug, if this is found to be the case this will be deleted
60-
options:
61-
- label: I agree i have checked the Issues Tab to see if this already Exists
62-
required: true
63-
- type: checkboxes
64-
id: terms
65-
attributes:
66-
label: Code of Conduct
67-
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/zakery292/monitormysolar/blob/main/.github/CODE_OF_CONDUCT.md).
68-
options:
69-
- label: I agree to follow this project's Code of Conduct
70-
required: true
1+
name: Bug Report
2+
description: Report an issue with the dongle, Home Assistant, or web monitoring.
3+
title: "[BUG] Brief description of the issue"
4+
labels: ["bug"]
5+
6+
body:
7+
- type: dropdown
8+
id: component
9+
attributes:
10+
label: "Affected Component"
11+
description: "Select the component related to your issue."
12+
options:
13+
- Dongle
14+
- Home Assistant
15+
- Web Monitoring
16+
validations:
17+
required: true
18+
19+
- type: input
20+
id: version
21+
attributes:
22+
label: "Version Information"
23+
description: "Enter the version of the integration or dongle firmware. Type N/A if related to Web Monitoring."
24+
placeholder: "Enter version here"
25+
validations:
26+
required: true
27+
28+
- type: textarea
29+
id: images_videos
30+
attributes:
31+
label: "Media Attachments"
32+
description: "Provide links to any images or videos showing the issue, if applicable."
33+
placeholder: "Paste links to images or videos here"
34+
validations:
35+
required: true
36+
37+
- type: textarea
38+
id: mqtt_output
39+
attributes:
40+
label: "MQTT Output"
41+
description: "If the issue relates to the Dongle, Home Assistant, or Web Monitoring, provide the MQTT output from `dongleID/status`."
42+
placeholder: "Paste MQTT output here"
43+
render: shell
44+
validations:
45+
required: true
46+
47+
- type: textarea
48+
id: detailed_description
49+
attributes:
50+
label: "Detailed Description"
51+
description: "Provide a detailed description of the issue, including steps to reproduce and the expected behavior."
52+
placeholder: "Describe the issue in detail"
53+
validations:
54+
required: true
55+
- type: checkboxes
56+
id: issue_check
57+
attributes:
58+
label: Issues
59+
description: By Submitting this Issue you confirm you have checked to see if the issue already exists and your not duplicating the bug, if this is found to be the case this will be deleted
60+
options:
61+
- label: I agree i have checked the Issues Tab to see if this already Exists
62+
required: true
63+
- type: checkboxes
64+
id: terms
65+
attributes:
66+
label: Code of Conduct
67+
description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/zakery292/monitormysolar/blob/main/.github/CODE_OF_CONDUCT.md).
68+
options:
69+
- label: I agree to follow this project's Code of Conduct
70+
required: true

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
blank_issues_enabled: false
2-
contact_links:
3-
- name: "General Support"
4-
url: "https://github.com/zakery292/monitormysolar/issues"
5-
about: "For help unrelated to bugs or feature requests."
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: "General Support"
4+
url: "https://github.com/zakery292/monitormysolar/issues"
5+
about: "For help unrelated to bugs or feature requests."
Lines changed: 51 additions & 51 deletions
Original file line numberDiff line numberDiff line change
@@ -1,51 +1,51 @@
1-
name: Dongle Feature Request
2-
description: Suggest a new feature or enhancement for the dongle.
3-
title: "[Dongle Feature] Brief description of the feature"
4-
labels: ["enhancement", "dongle"]
5-
6-
body:
7-
- type: input
8-
id: feature_name
9-
attributes:
10-
label: "Feature Name"
11-
description: "Give a brief name for the feature you’re requesting."
12-
placeholder: "Enter feature name here"
13-
validations:
14-
required: true
15-
16-
- type: dropdown
17-
id: UI_Firmware
18-
attributes:
19-
label: "UI Or Firmware Feature?"
20-
options:
21-
- UI
22-
- Firmware
23-
validations:
24-
required: true
25-
26-
- type: textarea
27-
id: feature_description
28-
attributes:
29-
label: "Feature Description"
30-
description: "Provide a detailed description of the feature and how it would improve the dongle’s functionality."
31-
placeholder: "Describe the feature in detail"
32-
validations:
33-
required: true
34-
35-
- type: textarea
36-
id: usage_scenarios
37-
attributes:
38-
label: "Usage Scenarios"
39-
description: "Explain scenarios where this feature would be useful."
40-
placeholder: "List possible use cases"
41-
validations:
42-
required: true
43-
44-
- type: input
45-
id: firmware_version
46-
attributes:
47-
label: "Current Firmware Version"
48-
description: "Provide the current firmware version, if applicable."
49-
placeholder: "Enter firmware version"
50-
validations:
51-
required: false
1+
name: Dongle Feature Request
2+
description: Suggest a new feature or enhancement for the dongle.
3+
title: "[Dongle Feature] Brief description of the feature"
4+
labels: ["enhancement", "dongle"]
5+
6+
body:
7+
- type: input
8+
id: feature_name
9+
attributes:
10+
label: "Feature Name"
11+
description: "Give a brief name for the feature you’re requesting."
12+
placeholder: "Enter feature name here"
13+
validations:
14+
required: true
15+
16+
- type: dropdown
17+
id: UI_Firmware
18+
attributes:
19+
label: "UI Or Firmware Feature?"
20+
options:
21+
- UI
22+
- Firmware
23+
validations:
24+
required: true
25+
26+
- type: textarea
27+
id: feature_description
28+
attributes:
29+
label: "Feature Description"
30+
description: "Provide a detailed description of the feature and how it would improve the dongle’s functionality."
31+
placeholder: "Describe the feature in detail"
32+
validations:
33+
required: true
34+
35+
- type: textarea
36+
id: usage_scenarios
37+
attributes:
38+
label: "Usage Scenarios"
39+
description: "Explain scenarios where this feature would be useful."
40+
placeholder: "List possible use cases"
41+
validations:
42+
required: true
43+
44+
- type: input
45+
id: firmware_version
46+
attributes:
47+
label: "Current Firmware Version"
48+
description: "Provide the current firmware version, if applicable."
49+
placeholder: "Enter firmware version"
50+
validations:
51+
required: false

0 commit comments

Comments
 (0)