Device status updates - #11722
Open
katarzyna-koltun-mx wants to merge 1 commit into
Open
Conversation
| * Bluetooth - Bluetooth devices are scanned continuously. They are considered available if seen, and unavailable if not seen for 30 seconds. | ||
| * Printer - The Client polls the system printer list. The scan only checks that the device exists, not its status, configuration, or connectivity. | ||
| * Serial device - The Client polls the system port list. The scan only checks that the device exists, not its connectivity. | ||
| * TCP/IPT client - The Client only checks that the host is defined and the port is valid. It cannot verify remote connectivity without actually connecting. |
Comment on lines
+40
to
+44
| * Errors - Any errors captured for this device. Devices that have thrown an error can be available, but cannot be connected, because the current connection is closed on error. The following error types may be logged: | ||
|
|
||
| * `Open_By_Other` - The connection was closed to allow connection by another Client. | ||
| * `Connection_Error` - The connection was closed unexpectedly. | ||
| * `Device_Error` - There was a device error. |
Contributor
There was a problem hiding this comment.
Suggested change
| * Errors - Any errors captured for this device. Devices that have thrown an error can be available, but cannot be connected, because the current connection is closed on error. The following error types may be logged: | |
| * `Open_By_Other` - The connection was closed to allow connection by another Client. | |
| * `Connection_Error` - The connection was closed unexpectedly. | |
| * `Device_Error` - There was a device error. | |
| * Error status - Shows any error captured for this device. Error status is reset on config change or reconnect. |
Errors don't necessarily prevent reconnect. The important thing is that devices cannot have status connected and errored at the same time. I don't think that's very important for our users to know, more for us.
The listed error types are only relevant for the connector. From the client POV, it only considers errors coming from the device and there is only a device error or no device error. The client doesn't consider an app connector disconnecting as an error but the connector does treat that as Connection_Error.
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
2 participants
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.
No description provided.