-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Continuous Warning: "[LATEST] Error receiving latest data: undefined is not a valid state value" #301
Comments
Maybe a firmware update on the Battery lead to this? At least on my eco8 it is running as usual. |
Please set adapter to debug and show data from the log line starting with |
My SB software version is 1.9.4.2021374, I don't think it changed in the last weeks, but I also don't exactly know since when the warning occurs. I already set the adapter to debug (and also to all) yesterday, but the message was only the same as it is in the screenshot above. |
Then I do not think, that the adapter is running on debug log level. In tab instances with expert mode you need to change the loglevel, maybe this helps: http://www.stueben.de/debugmodus-in-iobroker-aktivieren/ |
Ok you're right, something went wrong yesterday, here's the log you requested:
|
Hm okay, somehow |
Is this an issue caused by me, my battery or the adapter? |
The assumption until now was, that this information is delivered for all batteries that have the API. If no update for your battery is available only adapter can get rid of it. |
Are you using the v2 api so meaning you have provided an auth token in the instance settings? |
I don't know the difference between api v2 or other, but I am using an Auth-Token in these settings, yes. |
okay and if you restart it is not logging |
@foxriver76 okay, how should I proceed now? |
it is tracked and I know what to do, just need to find some time. |
Ok, thank you very much! |
Hi,
I get the warning above by the adapter every few sconds and always when it's running.
Am I the only one with this problem?
The text was updated successfully, but these errors were encountered: