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

[bug] Smart Start name and location doesn't flow to device on auto add. #1943

Closed
4 of 7 tasks
crzykidd opened this issue Nov 6, 2021 · 0 comments · Fixed by #1953
Closed
4 of 7 tasks

[bug] Smart Start name and location doesn't flow to device on auto add. #1943

crzykidd opened this issue Nov 6, 2021 · 0 comments · Fixed by #1953
Assignees
Labels
bug Something isn't working

Comments

@crzykidd
Copy link

crzykidd commented Nov 6, 2021

Checklist:

  • I am not using Home Assistant. Or: a developer has told me to come here.
  • I have checked the troubleshooting section and my problem is not described there.
  • I have read the changelog and my problem is not mentioned there.

Build/Run method

  • Docker
  • PKG
  • Snap package
  • Manually built (git clone - yarn install - yarn run build )

Zwavejs2Mqtt version: 5.11.0
Z-Wave JS version: 8.7.5

Describe the bug

Name and location from Smart Start doesn't get added to device after it has been included

To Reproduce

  1. Add Provisioning Entities to zwavejs2mqtt
  2. Update entry to include name and/or location
  3. connect device so it will auto provision.
  4. Device is added successfully, but name and location is not included.

Expected behavior

Device should be added and name/location used in Provisioning Entities should have been added to the record.

Additional context

Add any other context about the problem here.
The logs should show Node 8 being added with no name/location added.

Logs_Nodes_Provisioning.zip

@crzykidd crzykidd added the bug Something isn't working label Nov 6, 2021
robertsLando added a commit that referenced this issue Nov 10, 2021
#1953)

* fix: correctly set node name and location when present on provisioning

Fixes #1943

* fix: use dskToString to parse DSK code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants