You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently there is no easy was via console to report the connectivity health of devices in a system that implement ICommunicationMonitor
Describe the solution you'd like
Add a console command with corresponding formatted CrestronConsoleResponse that outputs the status of any devices that implement ICommunicationMonitor. Ensure the the output is easily machine parsable.
Describe alternatives you've considered
An HTTP request to deliver the same information (future)
@jgutenplan should be consulted on necessary data and preferred format for parsing via UDM lambda
The text was updated successfully, but these errors were encountered:
This command already exists: DEVCOMMSTATUS. However, it could be improved, as it is most likely NOT using CrestronConsole.ConsoleCommandResponse, and the output seems to be the type of the class, not a device key, and has some line-ending issues on 3-series.
I think the line ending issues are just going to be problematic, period. 3-series vs 4-series line endings aren't properly accounted for in Toolbox still and it makes for really ugly console output across the board, unfortunately.
Is your feature request related to a problem? Please describe.
Currently there is no easy was via console to report the connectivity health of devices in a system that implement ICommunicationMonitor
Describe the solution you'd like
Add a console command with corresponding formatted CrestronConsoleResponse that outputs the status of any devices that implement ICommunicationMonitor. Ensure the the output is easily machine parsable.
Describe alternatives you've considered
An HTTP request to deliver the same information (future)
@jgutenplan should be consulted on necessary data and preferred format for parsing via UDM lambda
The text was updated successfully, but these errors were encountered: