Display Status of GPIO Inputs on the Nav-Bar / Main Tab #359

New Issue

2020-10-24T14:24:18+01:00

RFBomb commented

2020-10-24 14:24:18 +01:00

(Migrated from github.com)

Is your feature request related to a problem? Please describe.
At the moment, there is no good way to evaluate if your inputs are working as intended. As far as I'm aware, the only real way to do this is the following:

Set up a GPIO output
Create 2 inputs (Rising Edge and Falling Edge) that both look at the same GPIO input
The 2 inputs both control the same output. Rising Edge turns output ON and falling edge turns output OFF.
Test the input, and check the status of the output as you change the state
(This can be done by turning on an LED with the debug-output you have set up, or by looking at the output state in the nav bar / main tab.)

Describe the solution you'd like
Any outputs that are created have their status shown in the nav bar, and they also show up as toggle-able in the main tab's UI. The inputs should be available for viewing in both of these locations as well. The inputs are already configured, and are already being polled. It is just a matter of displaying them.

Also, as far as I could tell, the inputs are unavailable in the API. From what I've read, you can view the status of and toggle the status of any output you like, but inputs are unavailable. I believe people might find it useful to be able to read the inputs in the same fashion with the API. You are able to perform 'GetOutputStatus' as an API call, but GetInputStatus does not work.

Furthermore, wouldn't it make sense to have the OutputStatus / InputStatus as part of that JSON package when you are looking at the /output /input API calls?

Describe alternatives you've considered
The rather time consuming workaround I posted in the top portion of the post is the only thing I've found that works, and its tedious to do, and obnoxious to troubleshoot.

Additional context
Add any other context or screenshots about the feature request here.

**Is your feature request related to a problem? Please describe.** At the moment, there is no good way to evaluate if your inputs are working as intended. As far as I'm aware, the only real way to do this is the following: - Set up a GPIO output - Create 2 inputs (Rising Edge and Falling Edge) that both look at the same GPIO input - The 2 inputs both control the same output. Rising Edge turns output ON and falling edge turns output OFF. - Test the input, and check the status of the output as you change the state (This can be done by turning on an LED with the debug-output you have set up, or by looking at the output state in the nav bar / main tab.) **Describe the solution you'd like** Any outputs that are created have their status shown in the nav bar, and they also show up as toggle-able in the main tab's UI. The inputs should be available for viewing in both of these locations as well. The inputs are already configured, and are already being polled. It is just a matter of displaying them. Also, as far as I could tell, the inputs are unavailable in the API. From what I've read, you can view the status of and toggle the status of any output you like, but inputs are unavailable. I believe people might find it useful to be able to read the inputs in the same fashion with the API. You are able to perform 'GetOutputStatus' as an API call, but GetInputStatus does not work. Furthermore, wouldn't it make sense to have the OutputStatus / InputStatus as part of that JSON package when you are looking at the /output /input API calls? **Describe alternatives you've considered** The rather time consuming workaround I posted in the top portion of the post is the only thing I've found that works, and its tedious to do, and obnoxious to troubleshoot. **Additional context** Add any other context or screenshots about the feature request here.

RFBomb commented

2020-10-25 02:04:52 +00:00

(Migrated from github.com)

I have created a pull request to resolve the suggestion about the API. I still request the display on the web interface though, since I don't know how to do that.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Gandalf/OctoPrint-Enclosure#359