You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My Landroid logs serveral messages I would consider to fit better into debug level. 2020-04-28 13:54:57.144 [INFO ] [orxlandroid.internal.mqtt.AWSMessage] - onSuccess
Is not really related to items changed, not sure what it means.
2020-04-28 13:54:57.687 [INFO ] [.worxlandroid.internal.mqtt.AWSTopic] - onMessage: {"cfg":{"id":1,"lg":"it","tm":"13:54:56","dt":"28/04/2020","sc":{"m":1,"p":-60,"d":[["00:00",0,0],["11:00",300,1],["11:00",300,1],["11:00",300,1],["11:00",300,1],["11:00",300,1],["11:00",300,1]]},"cmd":0,"mz":[0,0,0,0],"mzv":[0,0,0,0,0,0,0,0,0,0],"rd":30,"sn":"xxxxxxxxxxxxxxxxx"},"dat":{"mac":"xxxxxxxxxxxxx","fw":3.52,"bt":{"t":25.2,"v":19.86,"p":100,"nr":1417,"c":0,"m":0},"dmp":[-2.6,-0.2,340.7],"st":{"b":35441,"d":597350,"wt":36995},"ls":1,"le":5,"lz":0,"rsi":-62,"lk":1}} 2020-04-28 13:57:16.360 [INFO ] [id.internal.WorxLandroidMowerHandler] - HOME | StatusCode: 1 - Home 2020-04-28 13:57:16.360 [INFO ] [id.internal.WorxLandroidMowerHandler] - NO_ERROR | ErrorCode: 0 - No error
This shows the whole data pulled from AWS, which can be made available via separate items, which will then show in events.log. Also ERROR is a reserved word for frontal which will mark the log line in red color as it would be an error message.
As an interim solution to avoid these messages I have set the log level to WARN.
The text was updated successfully, but these errors were encountered:
My Landroid logs serveral messages I would consider to fit better into debug level.
2020-04-28 13:54:57.144 [INFO ] [orxlandroid.internal.mqtt.AWSMessage] - onSuccess
Is not really related to items changed, not sure what it means.
2020-04-28 13:54:57.687 [INFO ] [.worxlandroid.internal.mqtt.AWSTopic] - onMessage: {"cfg":{"id":1,"lg":"it","tm":"13:54:56","dt":"28/04/2020","sc":{"m":1,"p":-60,"d":[["00:00",0,0],["11:00",300,1],["11:00",300,1],["11:00",300,1],["11:00",300,1],["11:00",300,1],["11:00",300,1]]},"cmd":0,"mz":[0,0,0,0],"mzv":[0,0,0,0,0,0,0,0,0,0],"rd":30,"sn":"xxxxxxxxxxxxxxxxx"},"dat":{"mac":"xxxxxxxxxxxxx","fw":3.52,"bt":{"t":25.2,"v":19.86,"p":100,"nr":1417,"c":0,"m":0},"dmp":[-2.6,-0.2,340.7],"st":{"b":35441,"d":597350,"wt":36995},"ls":1,"le":5,"lz":0,"rsi":-62,"lk":1}}
2020-04-28 13:57:16.360 [INFO ] [id.internal.WorxLandroidMowerHandler] - HOME | StatusCode: 1 - Home
2020-04-28 13:57:16.360 [INFO ] [id.internal.WorxLandroidMowerHandler] - NO_ERROR | ErrorCode: 0 - No error
This shows the whole data pulled from AWS, which can be made available via separate items, which will then show in events.log. Also ERROR is a reserved word for frontal which will mark the log line in red color as it would be an error message.
As an interim solution to avoid these messages I have set the log level to WARN.
The text was updated successfully, but these errors were encountered: