V1.7: Error messages in Service status about pyess

[gluap]

@fu-zhou yes you can still work with the command line!
Actually I guess this is not even a new issue - It is one of the locations where I added extra logging in order to find out whether they cause #7.

I'll look into it, pretty sure it can be fixed quickly.

[fu-zhou]

Ah, okay, the additional logging then idientified the two issues:
TypeError: string indices must be integers
ERROR:pyess.essmqtt:exception while sending to mqtt

The ERROR is maybe a result of the TypeError?

[gluap]

@fu-zhou yes, the full multiline message is the result of the same TypeError - the logging I added displays all the lines together. I was hoping to find the cause for the hangups this way, by also displaying the stacktrace. The issue debugging is that with asyncio it easily happens that one does not notice that an exception happens somewhere unless it is caught explicitly. My guess was that the mqtt send loop was crashing without saying good bye so I added logging therein. That logging indeed exposed an issue on your end (but not #7).

0.1.8 should fix this new issue as far as I can tell. The error you describe above does not happen on my ess, likely because the structure of /home/ and /common/ daata sources differs between our ESSes.

I know about the potentially appearing new log message

INFO:pyess.aio_ess:fetching auth key
 /home/pi/pyess/venv/lib/python3.7/site-packages/aiohttp-4.0.0a1-py3.7-linux-aarch64.egg/aiohttp/client.py:977: RuntimeWarning: coroutine 'noop' was never awaited
   self._resp.release()
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

If it appears on your end that should not be a cause for concern -- it is a bug in aiohttp that will likely be fixed in a future version of their package, but that shouldn't cause issues apart from displaying the message.

[fu-zhou]

Got v1.8 installed - runs smooth, no error messages!
I run the Enervu App v1.2.4, got the LG ESS Home 8 System with 9.8 kWh battery and all 3 strings attached. For home and common Home 8 and 3 strings should set the communication frame.

[gluap]

The meaning of this sentence is unclear to me:

For home and common Home 8 and 3 strings should set the communication frame.

My guess is you're summarizing what system the original issue occured for right? I'm asking because the "should" might also refer to what pyess should do but doesn't, indicating some persisting issue.

[fu-zhou]

You mentioned that The error you describe above does not happen on my ess, likely because the structure of /home/ and /common/ daata sources differs between our ESSes.
What I meant to say is that the contents of the common and home section "should" depend on the system one has and how many strings are connected. I.e. if your system and my system has the same configuration, there shouldn't be any difference in home and common. That's all, I didn't intend to summarize what system the original issue occured for. And also no intend to point out what pyess should do but doesn't. The "should" just came from my guess.

[gluap]

I fully agree, it should depend on the system :) Very good, sorry I didn't get it on the first try. Thank you for the clarification, closing this issue now.