Skip to content
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

SML parsing error #11

Open
umatz opened this issue Oct 8, 2024 · 0 comments
Open

SML parsing error #11

umatz opened this issue Oct 8, 2024 · 0 comments

Comments

@umatz
Copy link

umatz commented Oct 8, 2024

First of all many thanks for this project. With the information of https://github.com/micw/homedatabroker/issues/3 I was able to set up homedatabroker for my use case, read data from a tibber pulse and export it via MQTT for further use (in my case feeding into volkszaehler).

When I check the log I see sml parsing errors every few minutes (no fix interval):

2024-10-08T13:23:21.143+02:00  WARN 1 --- [   scheduling-3] d.w.h.s.TibberPulseHttpSource.pulse      : Unable to parse SML from response

java.io.IOException: Invalid SML payload: 1b1b1b1b010101017605010203046200620072650000010176010b0a014c4f4700057cf3bb05010203040b0000000000000000000072620165020f78d90163c633007605010203046200620072650000070177010b0a014c4f4700057cf3bb070100620affff72620165020f78d9f106770701006032010101010101044c4f470177070100600100ff010101010b0a014c4f4700057cf3bb0177070100010800ff65001c110401621e52ff690000000004967f4b0177070100020800ff0101621e52ff690000000000009c920177070100100700ff0101621b520059000000000000025a0177070100240700ff0101621b520059ffffffffffffffc70177070100380700ff0101621b520059000000000000020b01770701004c0700ff0101621b52005900000000000000880177070100200700ff0101622352ff6900000000000009520177070100340700ff0101622352ff6900000000000009420177070100480700ff0101622352ff69000000000000094301770701001f0700ff0101622152fe6900000000000000
	at de.wyraz.tibberpulse.sml.SMLDecoder.extractMessage(SMLDecoder.java:289) ~[classes!/:1.0.0-SNAPSHOT]
	at de.wyraz.tibberpulse.sml.SMLDecoder.decode(SMLDecoder.java:55) ~[classes!/:1.0.0-SNAPSHOT]
	at de.wyraz.tibberpulse.sml.SMLDecoder.decode(SMLDecoder.java:46) ~[classes!/:1.0.0-SNAPSHOT]
	at de.wyraz.homedatabroker.source.TibberPulseHttpSource.schedule(TibberPulseHttpSource.java:56) ~[classes!/:1.0.0-SNAPSHOT]
	at de.wyraz.homedatabroker.source.AbstractScheduledSource.lambda$start$0(AbstractScheduledSource.java:20) ~[classes!/:1.0.0-SNAPSHOT]
	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-6.0.9.jar!/:6.0.9]
	at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:96) ~[spring-context-6.0.9.jar!/:6.0.9]
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[na:na]
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[na:na]
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1135) ~[na:na]
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[na:na]
	at java.base/java.lang.Thread.run(Thread.java:831) ~[na:na]

Is it possible to identify the cause of the parsing error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant