Query on time registers #65

As a followup to #62, I've now integrated your integration into Pv_opt (https://github.com/fboundy/pv_opt) as an option for controlling Solis inverters via SolisCloud and its under beta test.

My understanding of "After changing an inverter setting, the integration reads back the updated value from the inverter to verify that the change was applied successfully" means that if I use AppDaemons "Call_service" functionality (essentially the HA action "Text: Set value") then this will wait for inverter ringback before giving a response?

It appears that way as the response from Appdaemons "call_service" is the following:

Result of call_service is {'id': 7946, 'type': 'result', 'success': True, 'result': {'context': {'id': '01K1YE95W708QRHDB7B73ZVN5K', 'parent_id': None, 'user_id': '6d27b37a82da4e1f9c7f0be1f0e5610b'}}, 'ad_status': 'OK', 'ad_duration': 4.243782655335963}

The ad_duration field is the number of seconds it takes to return the response (I think!) which most of the time is around the 4-5 second mark. This feels right if solis-cloud-control writes to SolisCloud via API, then the inverter, then wait for the inverter to respond, then tell the API, then respond back to solis-cloud-control.

The issue however is that occasionally appdaemon times this out, as it has a limit of 10seconds for updating HA entities (which cannot be changed).
The message produced is

06/08, 01:20:58 WARNING HASS: Timed out [0:00:10] waiting for request: {'type': 'call_service', 'domain': 'text', 'service': 'set_value', 'service_data': {'value': '01:30-01:30'}, 'target': {'entity_id': 'text.solis_slot1_discharge_time'}, 'id': 6477}

It is a warning, and the write does go through to the inverter. My query is, if I were to access your integration via a custom service action as offered in #62, do you think this will improve things? (I've read that using the HA actions services are pretty slow). I guess my question really is, what is the average time delay in seconds that the verifies usually take?