Skip to content

sync usb_path to other docs #4439

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

Merged
merged 2 commits into from
Jan 25, 2018
Merged

Conversation

Guyanthalas
Copy link
Contributor

The hassio zwave documents reference usb_path: /dev/ttyACM0, so this document should be in sync. After some discussion it appears that this could be variable, in which case there should be a good way to figure out the CORRECT answer rather than using a guess as example code without stating it as such. Possibly linking back to the linux "how to find" section?

Description:

Pull request in home-assistant (if applicable): home-assistant/home-assistant#

Checklist:

  • Branch: Fixes, changes and adjustments should be created against current. New documentation for platforms/components and features should go to next.
  • The documentation follow the standards.

The hassio zwave documents reference usb_path: /dev/ttyACM0, so this document should be in sync. After some discussion it appears that this could be variable, in which case there should be a good way to figure out the CORRECT answer rather than using a guess as example code without stating it as such. Possibly linking back to the linux "how to find" section?
@nicxvan
Copy link
Contributor

nicxvan commented Jan 17, 2018

I just dealt with this process myself.
I added the steps that I used here: https://community.home-assistant.io/t/help-setting-up-aeotec-z-stick-gen5-z-wave-plus-usb-stick/39175/17?u=nicxvan

If you want I can look at adding some of this information. I just wasn't sure where to do that. I do have another open PR that adds some info about enabling the serial interface for RPI.

```

For some devices the `/dev/ttyAMA0` device is not detected by udev and is therefore not mapped by Docker. To explicitly set this device for mapping to Home-Assistant, execute the following command using the ssh add-on:
For some devices the `/dev/ttyACM0` device is not detected by udev and is therefore not mapped by Docker. To explicitly set this device for mapping to Home-Assistant, execute the following command using the ssh add-on:
Copy link
Member

Choose a reason for hiding this comment

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

No longer true for Hass.io 0.80, since it will automatically map all devices.

@Guyanthalas
Copy link
Contributor Author

I've removed the language that no longer applies.

@frenck frenck requested a review from pvizeli January 20, 2018 15:26
@frenck
Copy link
Member

frenck commented Jan 25, 2018

Great thx! Merging...

@frenck frenck merged commit f7c2c1a into home-assistant:current Jan 25, 2018
@Guyanthalas Guyanthalas deleted the patch-2 branch January 25, 2018 22:30
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.

4 participants