2.2.4.141 Motion Lighting with Hub Mesh errors

Trying out Hub Mesh and getting this error OCCASIONALLY. Trying this out in my office lighting where I sit now most of the day so it gets hammered pretty good. Lighting is working..so maybe this is expected but thought I'd point it out:

2020-11-18 09:46:43.648 am [error](http://192.168.13.40/installedapp/configure/930)java.lang.NullPointerException: null (motionInactive)

I'm also seeing some errors with a SCENE that has hubmesh items in it also.

[app:3396](http://192.168.13.40/logs#app3396)2020-11-18 09:37:28.629 am [error](http://192.168.13.40/installedapp/configure/3396)java.lang.NullPointerException: null (checkScene)

Again, the scene seems to be working.

1 Like

@gopher.ny looks like we found another like me ! :slight_smile: hopefully we can find some similarities between the systems to find the cause?

I have tons of repeatable logs...by repeatable I mean it happens often...but not consistently if that makes sense.

Have so far seen similar errors on motion sensors, scene lighting and locks.

Iā€™m seeing this error with all scenes that have hub mesh lights.

Do any of these errors show line numbers in the logs? Please use screenshots, not copy paste, to show logs.

image

some examples, I see no line numbers

Thanks, we're looking into it..

Going to rachet up debug logging on your hub, hopefully that will produce some line numbers.

1 Like

@gopher.ny feel free to have a look at my 2 hubs. The last screenshot is the Amazon Echo app.

Motion Lighting App

Groups and scenes

1 Like

Iā€™m seeing those errors as well on .143

2.2.4.145 (just released) has some extra NullPointerException handling compared to 141 and 143. Please update whenever convenient and let me know, I'll monitor hubs logs for results.

1 Like

I updated my hubs. :crossed_fingers:

Ditto, still seeing the errors...

in addition...I went into one of my ML apps and hit "Done" just because...and I saw this in the logs:

1 Like

Yes indeed.

Do me a favor and open the parent app, Motion and Mode Lighting Apps, with logs running, hit Done, and see if it throws that error.

I get this when I do that.

What build are you on?

We know what's going on, and it relates to the change of the name of the parent app (Motion and Mode Lighting Apps). We will get a fix for it, and it will be released in a hot fix.

1 Like

I got the same error as @BorrisTheCat

Thanks for the update!