Parallel fixes

[jaredmauch]

Stashed branch that I am using in production. Intent is to resolve conflicts to make a cleaner PR to origin branch

[BuxtonCalvin]

I was reading through some of your code changes and it appears that you're considering multiple transports for outgoing data. Is that for a single inverter data read? Or is the locking code for multiple reads /parallel inverter reads? Anyway, I'm interested in the idea of a multi-transport out setup so as not to spam my network with unnecessary data fields, but the original author is not interested and doesn't have the time. So I'm getting it done by spinning up three distinct containers, one for type of transport. Which is probably not so healthy for the inverter API. As well, I was considering writing a timescaledb transport based on your influx transport, but it appears from your other EG4 project that you're already using postgres (without the timescaledb extension). Any chance on you writing a timescaledb transport, as I can see from your changes that you would do it a million times better than I could. Thx