Skip to content

add documentation note for Q3D support in dsmr#21111

Closed
Aeroid wants to merge 40 commits into
home-assistant:nextfrom
Aeroid:dsmrQ3D
Closed

add documentation note for Q3D support in dsmr#21111
Aeroid wants to merge 40 commits into
home-assistant:nextfrom
Aeroid:dsmrQ3D

Conversation

@Aeroid
Copy link
Copy Markdown
Contributor

@Aeroid Aeroid commented Jan 9, 2022

Proposed change

Documentation note for Q3D support in DSMR integration

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

  • Link to parent pull request in the codebase: #63669
  • Link to parent pull request in the Brands repository:
  • This PR fixes or closes issue:

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.

frenck and others added 30 commits December 30, 2021 13:21
The orginal had captial Z and M where there shouldn't be.
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Co-authored-by: Shay Levy <levyshay1@gmail.com>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Co-authored-by: Franck Nijhof <frenck@frenck.nl>
Add details on how to access the Z-Wave JS logs. Note: I'm not sure about the prevailing (best) way to indicate the path to an option in the GUI. I've followed close to the other example on this page, but adjusted slightly to provide current UI and additional detail.
@Aeroid
Copy link
Copy Markdown
Contributor Author

Aeroid commented Jan 9, 2022

stuck in rebase ... is there a quick way thru the merge conflicts? ... sorry, this is also new to me.

@RobBie1221
Copy link
Copy Markdown
Contributor

I think you broke it. You should rebase and force push changes. Perhaps it's easier to close this pull and create a new one where you start a branch from next instead of current.

@Aeroid
Copy link
Copy Markdown
Contributor Author

Aeroid commented Jan 9, 2022

I think you broke it. You should rebase and force push changes. Perhaps it's easier to close this pull and create a new one where you start a branch from next instead of current.

think so to -> #21113

@Aeroid Aeroid closed this Jan 9, 2022
@probot-home-assistant probot-home-assistant Bot removed needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch in-progress This PR/Issue is currently being worked on labels Jan 9, 2022
@github-actions github-actions Bot locked and limited conversation to collaborators Jan 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla-signed current This PR goes into the current branch has-parent This PR has a parent PR in another repo

Projects

None yet

Development

Successfully merging this pull request may close these issues.