Skip to content

doc: Should check unconfigured state before running fastscan #290

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.

Sign up for GitHub

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
acolomb merged 3 commits into from
May 7, 2026
Merged

doc: Should check unconfigured state before running fastscan #290

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0266731
Update lss.rst
ymkim92 Dec 15, 2021
2217489
Apply suggestion from @christiansandberg
friederschueler May 7, 2026
3663a24
whitespace
acolomb May 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions doc/lss.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ Or, you can call this method with 4 IDs if you want to switch only one slave::
Or, you can run fastscan procedure ::

ret_bool, lss_id_list = network.lss.fast_scan()

**NOTE**: Before you run fastscan, you have to make sure the devices are in non-configured or unconfigured state.
Comment thread
friederschueler marked this conversation as resolved.
Outdated

Once one of sensors goes to CONFIGURATION state, you can read the current node id of the LSS slave::

Expand Down