-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V1.7: Error messages in Service status #8
Comments
Ah, okay, the additional logging then idientified the two issues: The ERROR is maybe a result of the TypeError? |
@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 I know about the potentially appearing new log message
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. |
Got v1.8 installed - runs smooth, no error messages! |
The meaning of this sentence is unclear to me:
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. |
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. |
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. |
I installed V1.7, MQTT communication with the server works however the following error messages are shown in
systemctl status essmqtt
:everytime I look into the status, the errors have the current time stamp, i.e. it seems as if the errors occur continously.
From what I understood the config file is optional, I can still work with the command line, right?
The text was updated successfully, but these errors were encountered: