Keep connection open to klf about pyvlx HOT 5 CLOSED

@ahorseman - I am as well rarely using Python and never digged deeper into it, so I stumbled upon similar questions. Some time ago, I set up PyVLX and have now made my efforts public and hope this helps you as well: https://github.com/werner-j/vlxcontrol

from pyvlx.

@werner-j : in your example, i find the name main pretty confusing. You should rename it to init_pyvlx or similar.

I would also position the if __name__ == '__main__': at the very end of the file and put the run command within this block.

But the most importand: Why didn't you use an async webserver framework? You should have a look at https://aiohttp.readthedocs.io/en/stable/ ("Server example")

from pyvlx.

Thank you for your hints @Julius2342. I've done some updates to it.

from pyvlx.

I experienced the same issue on my environment at home and I did not trace down the reason why.

pyvlx "should" keep the connection open with a heart beat mechanism. Within Home-assistant i enabled the logging for pyvlx by adding:

logger:
  default: warning
  logs:
    pyvlx: debug

I then see in my logs the following requests:

2019-06-25 12:17:21 DEBUG (MainThread) [pyvlx] SEND: <FrameGetStateRequest/>
2019-06-25 12:17:21 DEBUG (MainThread) [pyvlx] REC: <FrameGetStateConfirmation gateway_state="GatewayState.GATEWAY_MODE_WITH_ACTUATORS" gateway_sub_state="GatewaySubState.IDLE"/>
2019-06-25 12:18:21 DEBUG (MainThread) [pyvlx] SEND: <FrameGetStateRequest/>
2019-06-25 12:18:21 DEBUG (MainThread) [pyvlx] REC: <FrameGetStateConfirmation gateway_state="GatewayState.GATEWAY_MODE_WITH_ACTUATORS" gateway_sub_state="GatewaySubState.IDLE"/>

These requests should keep the connections open and reconnect if a connection died.

WRT to the fire and forget mechanism. there is such when sending a request to the API by adding node.close(wait_for_completion=False) to the call. But this won't skip the connection time it only does not wait until the device has reached its final position.

HTH

Julius

from pyvlx.

Thank you. That might be of help. Though I ask myself, whether that is really clean. Perhaps @Julius2342 can use that as additional example for PyVLX and help clean it? Closing the issue. Thank you.

from pyvlx.