Too expand on what mwalker suggested for the led behavior list, yes, that's exactly what I am going for. I don't mind if existing calls change the leds because after each command I can just set them to what the overall status is again anyways and seeing the existing calls in action is also a desired effect. The only other led behavior I would add is for them to flash all on and then off as a final "success" status.
I'll be honest and admit that I am a python and bash person and C(++) is not my strong suit at all. I'll try struggle bus'ing with this and see if I can contribute a simple feature request as a way to get my feet wet with contributing to a great project and learning C(++).
]]>While I agree it could be done, you would need to update all the OS calls to LED x on/off to be disabled IF the user actions something. if this is not done, then they may get turned on/off by existing code.
I am just brain storming here.
But something like LED_A (status), LED_B (status), LED_C (status), LED_D (status)
Where status could be
0 - As per existing code/OS control.
1 - User Turned On (OS will ignore existing calls)
2 - User Turned Off (OS will ignore existing calls)
Given the above, then do we need to consider some way to auto return to OS status calls (e.g. power cycle the unit would do it), but if you turn them all off, and forget to return control to the OS then you may think the unit is off/lost power (non rdv4). Would that be ok?
Just some thoughts.
]]>Thanks
]]>Thanks
]]>