Harden LAN scanner discovery and device classification - #163
Merged
Conversation
divadiow
marked this pull request as ready for review
July 25, 2026 04:33
divadiow
marked this pull request as draft
July 26, 2026 20:09
divadiow
marked this pull request as ready for review
July 26, 2026 21:18
Contributor
Author
Owner
|
Nice, pls forum topic about scanner for GuideS? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
255.255.255.255without integer wraparoundlastHTTPJSONtext.txtwrite from discovery parsingSDK=obkdevices as OBK while retaining Tasmota discoveryWhy
The scanner could report completion before its final HTTP requests were consumed, so responsive devices at the end of a scan could be omitted. Input values were effectively unbounded, right-click actions could use a stale focused row, and concurrent discovery depended on writing every JSON response to one shared debug filename.
OBK and Tasmota discovery both begin with the Tasmota-compatible
STATUS 0endpoint. The OBK branch was nevertheless setting the Tasmota flag totrue, which routed OBK devices through the Tasmota mass-backup path.Impact
Scans now finish with complete results, reject unsafe ranges and concurrency settings, and apply context-menu actions to the intended device. OBK devices follow the OBK backup path, while genuine Tasmota devices remain classified as Tasmota.
Validation
lastHTTPJSONtext.txtwas held exclusively open/24scan found 8 compatible devices: 7 OBK and 1 genuine Tasmota, all classified correctlySTATUS 0and/api/inforequests; no reboot or control commands were sent