-
Notifications
You must be signed in to change notification settings - Fork 17
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
Positive Value eventhough sun not shining and inverter in sleep mode #74
Comments
Can you provide the output of the Grott logs during this time please? All this integration does is format and present those values in a consumable way. |
Sorry for the question, how to find the logs? |
It depends on how you're running grott. |
I run Grott as an integration, the inverter is a Mic850 the the values which are not set to 0 are sensor.fsj4cdk07u_phase_1_power and fsj4cdk07u_generated_energy_today, these get "0" when inverter is online again next day... |
Generated energy today shouldn't reset to 0 because it's an increasing total for the day. Phase 1 power should go down to zero though as you suggest. I assume you mean you run grott as an add-on i.e. this one: https://github.com/egguy/grott-home-assistant-add-on if that's the case then the logs should be visible as part of the add-on itself or in the Home Assistant logs. The sort of thing I'm looking for is like this (a copy from my own logs):
|
OK this is exactly what I am using! But in system/logs i only see Grott Beta branch (2.8) |
I'm not sure I thought the logs should appear there, @egguy are you able to help me here with how to see the Grott logs from your addon? |
Got it, here it is: LOG:
|
So the The problem I have is that this integration just presents the values from Grott. Therefore I'd recommend posting an issue over in the grott repo here: https://github.com/johanmeijer/grott/issues/ and reference this one. |
Hello,
how can this issue be solved, that wenn inverter is offline still a positive wattage value remains... see pic
Thank you
The text was updated successfully, but these errors were encountered: